Export
VU#948176
/wiki/vu-948176
The link always opens the latest version of this page.
Ask an AI about it
Open in ChatGPTA new chat that reads this entry from the site Open in ClaudeThe same, in Claude
Sending this to someone?
MarkdownPlain text for notes apps and AI chats
WordA document to edit and annotate
PDFA4, for printing and sharing
ZIPEverything: the documents, the data, and instructions for AI assistants
Share the link instead of a file, and they will always see the latest version.
Files are a snapshot of today. The live page has anything newer.
growing ·
3 feeds
VU#948176
Multiple TLS libraries disagree on X.509 Name Constraints validation in certificate chains
Snapshot
- KEV
- no 1 source
- Weakness
- Name Constraints 1 source
- Disclosed
- 2026-10-14 1 source
Intelligence coverage
Multiple TLS libraries disagree on X.509 Name Constraints validation in certificate chains.
Drawn from 3 news sources; the facts and relationships below show where each detail comes from.
Facts 3
| Attribute | Value | Confidence | Sources | Cited |
|---|---|---|---|---|
| KEV | no | low | 1 | 2 |
| Weakness | Name Constraints | low | 1 | 2 |
| Disclosed | 2026-10-14 | low | 1 | 2 |
Frequently mentioned together 6
Sources 3
- What Is an X.509 Certificate, and Why Can TLS Libraries Disagree? · LinuxSecurity: Features
- What Is an X.509 Certificate, and Why Can TLS Libraries Disagree? · LinuxSecurity: Articles
- VU#948176: Multiple TLS libraries can bypass delegation enforcement · CERT/CC Vulnerability Notes