What is CVE-2026-71889?

CVE-2026-71889 is PKIXCertPathReviewer does not apply X.509 name constraints to the target certificate. The supplied enrichment data classifies it as Cryptography mapped to CWE-295 CWE-295.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-71889. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-71889 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

2 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-71889 using CVSS 8.7, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

highCryptographypublic exploit

CVE-2026-71889

CVE-2026-71889 — PKIXCertPathReviewer does not apply X.509 name constraints to the target certificate

In Bouncy Castle for Java before 1.86, neither copy of PKIXCertPathReviewer - org.bouncycastle.pkix.jcajce.PKIXCertPathReviewer nor the legacy org.bouncycastle.x509.PKIXCertPathReviewer - applied X.509 name constraints to the end-entity certificate. checkNameConstraints walked the path with a loop bound of index greater than zero, which is the bound the CA-only steps require, but index zero is the target certificate under the standard CertPath ordering, so the permitted and excluded subtree checks of RFC 5280 sec. 6.1.3 (b) and (c) never ran against the leaf's subject DN or its subjectAltName. A chain whose leaf violated a NameConstraints extension imposed by its own issuing CA therefore reported isValidCertPath() true with an empty error list, while CertPathValidator.getInstance("PKIX", "BC"), which shares no code with the reviewer, rejected the identical chain against the identical trust anchor. An application using the reviewer to make the trust decision rather than for diagnostics alongside a real validation accepted a certificate the constrained CA was never authorised to issue. Both copies now check every certificate in the path including the target, waive the sec. 4.2.1.10 self-issued exemption for the final certificate as sec. 6.1.3 requires, and skip the sec. 6.1.4 (g) constraint-accumulation step for the target. This issue also affects Bouncy Castle for Java LTS before 2.73.13, which carries only the org.bouncycastle.pkix.jcajce copy of the reviewer. It also affects Bouncy Castle for Java FIPS (BC-FJA) before bcpkix-fips 1.0.13 (1.0.X series), 2.0.13 (2.0.X series) and 2.1.13 (2.1.X series).

Published Oct 3, 2026Updated Oct 3, 2026Sources: NVD, Legion of the Bouncy Castle Inc. (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

ahead of 0% of scored CVEs

Affects

Legion of the Bouncy Castle Inc.

6 products listed

CVSS base

8.7

high

Remediation

The vendor's own words where we have them.

Upgrade BC-JAVA to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Legion of the Bouncy Castle Inc.	BC-JAVA	0 to < 1.86	Vulnerable
Legion of the Bouncy Castle Inc.	BC-JAVA	0 to < 1.86	Vulnerable
Legion of the Bouncy Castle Inc.	BC-LTS-JAVA	2.73.0 to < 2.73.13	Vulnerable
Legion of the Bouncy Castle Inc.	BC-FJA	1.0.4 to < 1.0.13	Vulnerable
Legion of the Bouncy Castle Inc.	BC-FJA	2.0.0 to < 2.0.13	Vulnerable
Legion of the Bouncy Castle Inc.	BC-FJA	2.1.0 to < 2.1.13	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Scope

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
8.7	CVSS 4.0	high	—	—	Legion of the Bouncy Castle Inc. (CNA)

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/U:Amber

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-295 · Improper Certificate Validation

Bypass Protection Mechanism
Gain Privileges or Assume Identity::

Mitigation: Certificates should be carefully managed and checked to assure that data are encrypted with the intended owner's public key.

Weakness & attack patterns

CWE-295

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-475 · Signature Spoofing by Improper ValidationCAPEC-459 · Creating a Rogue Certification Authority Certificate

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable BC-JAVA, BC-LTS-JAVA, BC-FJA.
Monitor for scanner or exploit-pattern traffic after 2 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 8.7 (AV:N)
Oct 3, 2026 · NVD
Initial · CVE published
Oct 3, 2026 · NVD
Added · GHSA-hqqj-v58h-gr7x published (high)
Oct 3, 2026 · GitHub Security Advisory
CVE published by MITRE.
Oct 3, 2026 · SOCRadar CTI

References

4 on the record

github.com/bcgit/bc-java/commit/06dcff2f51037095de126986285c998e3455ab85
Exploit, Third Party Advisory, NIST
github.com/bcgit/bc-java/wiki/CVE%E2%80%902026%E2%80%9071889
Exploit, Third Party Advisory, NIST
nvd.nist.gov/vuln/detail/CVE-2026-71889
NVD
github.com/advisories/GHSA-hqqj-v58h-gr7x
Exploit, Third Party Advisory

Elsewhere on this site

Legion of the Bouncy Castle Inc.every CVE for this vendor
Cryptographysame class
CWE-295other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-71889 is PKIXCertPathReviewer does not apply X.509 name constraints to the target certificate, a high vulnerability affecting BC-JAVA, BC-LTS-JAVA, BC-FJA from Legion of the Bouncy Castle Inc.. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-71889. Public exploit evidence is: 2 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 8.7 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.