VU#410595: Google BoringSSL Name Constraints Bypass in SAN Validation Logic
2026-10-15T20:52:00Z•641c7d38902e8ab5b5271767e8ead2bccc5921fbaf68a6a2e3df4870ed2e48ab
CVE-2026-100156CVE-2026-104937CVE-2026-16753CVE-2026-34073CVE-2026-3547CVE-2026-3833CVE-2026-96679CVE-2026-96681BishengBoringSSLGnuTLSGoIDORKomodoLowcoderName-ConstraintsOS-command-injectionOpenSSLShopwareTLSX.509authentication-bypassauthorization-bypasscertificate-validationcross-tenant-data-exposureremote-code-executionroot-privilegesstored-XSStoken-theftwolfSSL
What happened
CERT/CC advisories describe multiple 2026 vulnerabilities, including authentication and authorization bypasses, cross-tenant data exposure, OS command injection as root, stored XSS enabling administrator token theft and potential RCE, and TLS/X.509 Name Constraints validation inconsistencies across libraries. The highest-impact issues enable unauthenticated administrative takeover or authenticated arbitrary command execution and infrastructure compromise.
Why it matters
A reviewed impact interpretation has not been published for this record.
Evidence and limitations
- Source ID
- certcc_vulnotes
- Record identifier
- 641c7d38902e8ab5b5271767e8ead2bccc5921fbaf68a6a2e3df4870ed2e48ab
- Enrichment time
- 2026-10-15T20:52:00Z
- AI-assisted enrichment
- Yes
This record may overlap with other records. Its enrichment can be incomplete or wrong, and machine assistance was used. Validate consequential decisions against the linked source and your own environment.