VU#862559: crypton-x509-validation Haskell libraries do not enforce X.509 NameConstraints
2026-06-17T20:52:22Z•f61023a573631f3216d7e8dba30b03178b34d9d219cbb7f2d257e43f02166c95
appsmithbyovdchrome-extensioncodemirrorcollibra-agent','zip-slip','path-traversal','unauthenticated-endcrypton-x509-validationdbxhardcoded-keyshaskellimsinsecure-transportintegrity-bypassipsecnameconstraintssecure-bootsensitive-data-exposureshimsipstored-xsstlsuefivolteweak-cryptox509xss
What happened
This document aggregates multiple recent vulnerability advisories affecting diverse platforms and components: crypton-x509-validation (Haskell TLS) fails to enforce X.509 NameConstraints allowing sub-CA impersonation (CVE-2026-9648); Microsoft-signed shim UEFI bootloaders can be abused to bypass Secure Boot (DBX mitigation planned); Securly Chrome extension (v3.0.7) contains insecure HTTP fetches, hardcoded AES keys, and exposed endpoints (CVE-2026-8874 / 8876 / 8878 / 8879) risking data exposure and manipulation; Verizon IMS VoLTE signaling lacked IPsec integrity protection enabling tampering
Why it matters
A reviewed impact interpretation has not been published for this record.
Evidence and limitations
- Source ID
- certcc_vulnotes
- Record identifier
- f61023a573631f3216d7e8dba30b03178b34d9d219cbb7f2d257e43f02166c95
- Enrichment time
- 2026-06-17T20:52:22Z
- 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.