Skip to content
Fencer Intel
critical 9.1

CVE-2026-9648 json

CVE-2026-9648

published 5mo ago modified 16d ago also EUVD-2026-36248 , HSEC-2026-0008

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 13%
public exploits
0
none known

Summary

The crypton-x509-validation Haskell library fails to enforce X.509 NameConstraints, allowing TLS clients to accept certificates whose Subject Alternative Names fall outside the issuing CA’s permitted subtrees. This oversight enables an attacker who compromises a name-constrained sub-CA to impersonate domains beyond its intended scope.

Patch / fix

  • hackage crypton-x509-validation 1.9.1
  • hackage crypton-x509 1.9.1
  • Haskell Programming Language crypton-certificate 1.9.1
  • ghc-aws openSUSE Tumbleweed 0.25.2-1.1
  • ghc-crypton-asn1-encoding openSUSE Tumbleweed 0.10.0-1.1
  • ghc-crypton-asn1-parse openSUSE Tumbleweed 0.10.0-1.1
  • ghc-crypton-asn1-types openSUSE Tumbleweed 0.4.1-1.1
  • ghc-crypton-pem openSUSE Tumbleweed 0.3.0-1.1
  • ghc-crypton-x509 openSUSE Tumbleweed 1.9.1-1.1
  • ghc-crypton-x509-store openSUSE Tumbleweed 1.9.0-1.1
  • ghc-crypton-x509-system openSUSE Tumbleweed 1.9.0-1.1

opensuse advisories openSUSE-SU-2026:11077-1openSUSE-SU-2026:11078-1openSUSE-SU-2026:11079-1openSUSE-SU-2026:11080-1openSUSE-SU-2026:11081-1openSUSE-SU-2026:11082-1

Is CVE-2026-9648 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
5mo ago

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OSV 3.1 6.8 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
hackage crypton-x509-validation
>=1.6.12, <1.9.1
1.9.1
hackage crypton-x509
>=1.7.6, <1.9.1
1.9.1
hackage x509-validation
>=1.4.0
no fix listed
hackage x509
>=1.4.0
no fix listed

Affected products

  • Haskell Programming Language crypton-certificate

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.