CVE-2026-59638
Bouncycastle Bc-Java ≤ 1.85
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:AmberCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-59638 is a critical-severity Improper Validation of Certificate with Host Mismatch (CWE-297) vulnerability in Bouncycastle Bc-Java. Its CVSS base score is 9.3 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Protocol or Service Impersonation (T1001.003); ranked at the 29th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-23 (Session Authenticity) and SC-8 (Transmission Confidentiality and Integrity) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-52016
Vulnerability Data
In Bouncy Castle for Java before 1.85, JSSE hostname verifier CN-fallback enabled by default despite documented opt-in. This issue also affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before bctls-fips 1.0.24 (1.0.X series),…
more
2.0.24 (2.0.X series) and 2.1.24 (2.1.X series).
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V17.2.8
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Protecting session authenticity structurally requires proper certificate validation to bind the presented certificate to the intended host.
Requiring confidentiality and integrity of transmitted data necessitates correct TLS certificate validation with host-name checking.
Security engineering principles require correct implementation of certificate validation (including hostname matching) when cryptography is used.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Protecting data-in-transit integrity depends on proper certificate validation to prevent MITM.
Secure development practices include coding correct certificate validation logic.
Server/service authentication via certificates directly requires correct host validation.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Security testing can detect missing certificate validation and host-mismatch checks.
Training can make developers aware that hostname verification is required and that pitfalls like NUL-byte handling and SAN/CN checks exist, but the weakness is an implementation defect (incorrect regex, truncation, missing checks) that training alone does not prevent — most instances arise from coding errors that require careful implementation and testing, not from ignorance of the requirement.
Secure coding practices include implementing proper certificate and hostname validation in code.
A.8.30 carries its effect through contractual requirements for secure design, coding and testing practices (8.25 to 8.29) applied to outsourced development, and CWE-297 is an ordinary software implementation weakness in certificate/hostname validation that those practices reach, the same way the CWE-134 anchor graded this clause at `partial`; the clause mandates a practice rather than a mechanism, so what it catches depends on the rigour of the supplier's implementation.
A.8.8's reach is DISCLOSURE — it finds vulnerabilities through published advisories and scanning for known flaws. CWE-297 does commonly surface as CVEs (multiple observed examples), so A.8.8 discovers that disclosed minority; the majority of certificate hostname-validation defects in deployed first-party code are never published and remain outside the clause's reach.