VU#410595: Google BoringSSL Name Constraints bypass in SAN validation logic
Cybersecurity Classified by Officially
Five Name Constraints findings in BoringSSL (VU#410595.8–.12) describe cases where certificate names may not be constrained as intended. Records .8, .9, .10 and .12 concern the legacy crypto/x509 path; .11 concerns the newer pki path. Two have been fixed, one is accepted, one is disputed, and one was declined. Name Constraints limit the names a subordinate certificate authority may issue. …
This is an extract. The publication continues at the source.
Read the original at the source: https://kb.cert.org/vuls/id/410595
Officially imported this from CERT Coordination Center’s own source and shows an extract. If you work there, claiming the profile and verifying the domain lets you choose to show the full text here.
This publication has changed since it was first published
2 versions recorded. The original is kept in full — nothing is overwritten.
- v2 imported change on current
- v1 as first published on Titled: “VU#410595: Google BoringSSL Name Constraints Bypass in SAN Validation Logic”
Provenance
- Organization
- CERT Coordination Center — imported from official source
- Official source
- https://www.kb.cert.org/vuls/atomfeed/ ATOM
- Imported
- October 14, 2026 16:00
- Versions
- 2 recorded
- Identity
-
https://kb.cert.org/vuls/id/410595