Security Resilience

CVE-2026-59652

Bouncycastle Bc-Java ≤ 1.85

Published
03 August 2026
Modified
23 October 2026
Patch / advisory
CVSS Score v4 6.9
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/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.0029 23th percentile
Risk Priority 41 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-59652 is a medium-severity LDAP Injection (CWE-90) vulnerability in Bouncycastle Bc-Java. Its CVSS base score is 6.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 23th 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 SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — 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, LDAP filter injection in legacy jdk1.4 LDAPStoreHelper.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1565 Data Manipulation Impact
Adversaries may insert, delete, or manipulate data in order to influence external outcomes or hide activity, thus threatening the integrity of the data.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-17507Same product: Bouncycastle Bc-Java
CVE-2026-12852Same product: Bouncycastle Bc-Java
CVE-2024-14041Same product: Bouncycastle Bc-Java
CVE-2023-33201Same product: Bouncycastle Bc-Java
CVE-2026-59644Same product: Bouncycastle Bc-Java
CVE-2026-12185Same product: Bouncycastle Bc-Java
CVE-2026-59643Same 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

Affected Assets

bouncycastle
bc-java
≤ 1.85

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)
  • V1.2.6

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Developer testing and evaluation can discover LDAP injection flaws through static analysis or crafted test cases.

Input validation directly stops untrusted data from reaching an LDAP query builder without neutralization of special characters.

Secure engineering principles require safe query construction and escaping that structurally prevents LDAP injection.

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.PS-06 mostly match
blocks

Secure SDLC practices directly require input neutralization and query parameterization to prevent LDAP injection.

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 in development catches LDAP injection via dynamic analysis or fuzzing, but does not prevent it at the source.

prevents

Training technical teams in proper input neutralization for LDAP queries can prevent some instances of LDAP injection, but developers are fallible and the strongest controls for this code-level defect are secure coding (A.8.28) and security testing (A.8.29); training moves a minority of instances, consistent with the A.6.3 vs CWE-598 anchor.

prevents

Secure coding standards require proper neutralization of LDAP special characters, directly eliminating this weakness.

finds

A.8.8's reach is DISCLOSURE — it sees only instances that carry a vendor-published flaw in third-party components. LDAP injection is primarily a first-party code defect, and the detection methods that reach it (static/dynamic analysis of source) belong to A.8.29, not A.8.8. A.8.8 finds it only where it surfaces as a published CVE in a third-party component, which is a minority of instances.

References