Security Resilience

CVE-2026-59638

Bouncycastle Bc-Java ≤ 1.85

Published
03 August 2026
Modified
28 August 2026
Patch / advisory
CVSS Score v4 9.3
Click a component to see what it means
Raw vectorCVSS: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:Amber
EPSS Score 0.0034 29th percentile
Risk Priority 45 floored blend · peak EPSS

CVSS 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

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

T1001.003 Protocol or Service Impersonation Command And Control
Adversaries may impersonate legitimate protocols or web service traffic to disguise command and control activity and thwart analysis efforts.
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
T1557.004 Evil Twin Credential Access
Adversaries may host seemingly genuine Wi-Fi access points to deceive users into connecting to malicious networks as a way of supporting follow-on behaviors such as [Network Sniffing](https://attack.
T1565.002 Transmitted Data Manipulation Impact
Adversaries may alter data en route to storage or other systems in order to manipulate external outcomes or hide activity, thus threatening the integrity of the data.
T1657 Financial Theft Impact
Adversaries may steal monetary resources from targets through extortion, social engineering, technical theft, or other methods aimed at their own financial gain at the expense of the availability of these resources for victims.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-59646Same product: Bouncycastle Bc-Java
CVE-2026-14682Same product: Bouncycastle Bc-Java
CVE-2026-12860Same product: Bouncycastle Bc-Java
CVE-2026-12816Same product: Bouncycastle Bc-Java
CVE-2026-12803Same product: Bouncycastle Bc-Java
CVE-2026-59651Same product: Bouncycastle Bc-Java
CVE-2026-12185Same product: Bouncycastle Bc-Java
CVE-2026-59650Same product: Bouncycastle Bc-Java
CVE-2026-8763Same product: Bouncycastle Bc-Java
CVE-2026-58062Same product: Bouncycastle Bc-Java

Affected Assets

bouncycastle
bc-java
≤ 1.85
bouncycastle
bctls-fips
1.0.0 — 1.0.24 · 2.0.19 — 2.0.24 · 2.1.20 — 2.1.24
bouncycastle
bouncy castle for java lts
≤ 2.73.11

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • 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.

PR.DS-02 mostly match
blocks

Protecting data-in-transit integrity depends on proper certificate validation to prevent MITM.

PR.PS-06 mostly match
blocks

Secure development practices include coding correct certificate validation logic.

PR.AA-03 partial match
blocks

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.

finds

Security testing can detect missing certificate validation and host-mismatch checks.

prevents

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.

prevents

Secure coding practices include implementing proper certificate and hostname validation in code.

prevents

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.

finds

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.

References