CVE-2026-71889

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (5th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — Patch released this week

Also known asEUVD-2026-91990 (ENISA EUVD) · GHSA-hqqj-v58h-gr7x (GitHub Security Advisories)Source: ENISA EUVD

8.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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).

CVSS
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
54
EG Risk 54/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 3, 2026

Last Modified

October 6, 2026

Advisory Details (2)

Auto-updated Oct 3, 2026
Patch available. Sources: github_commit.
GitHub commit

commit 06dcff2f5103 (bcgit/bc-java)

Fix landed in bcgit/bc-java commit 06dcff2f5103 — awaiting tagged release

https://github.com/bcgit/bc-java/commit/06dcff2f51037095de126986285c998e3455ab85
Web page

CVE‐2026‐71889 · bcgit/bc-java Wiki · GitHub

https://github.com/bcgit/bc-java/wiki/CVE%E2%80%902026%E2%80%9071889

Vendor and National Authority Advisories for CVE-2026-71889(19)

These vendors and national cybersecurity authorities published their own advisory mentioning this CVE — often with remediation steps + affected product lists not in NVD. An authority's is an excerpt, in the language it published it in, not translated, and credited to it with a link.

Patch Availability(15)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-modelmesh-rhel9:17933407462026-11-19redhat
redhateap8-ws-commons-XmlSchema-0:2.3.3-1.redhat_00001.1.el9eap2026-11-11redhat
redhatbcutil-jdk18on2026-11-11redhat
redhatocp-tools-4/jenkins-rhel9:17920401312026-10-22redhat
redhatocp-tools-4/jenkins-rhel8:17920443862026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920402872026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920400812026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920415142026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920407332026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920404282026-10-22redhat
redhatocp-tools-4/jenkins-rhel8:17920443262026-10-22redhat
redhatocp-tools-4/jenkins-rhel8:17920443822026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920400962026-10-22redhat
redhatocp-tools-4/jenkins-rhel8:17920443272026-10-22redhat
redhatorg.bouncycastle/bcpkix-jdk18on:1.86.0.redhat-000012026-10-15redhat

These rows come from Red Hat. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
bouncycastle1.72-2 ... 1.86-1 (6 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
bouncycastle1.80-3, 1.86-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
bouncycastle1.80-3
  • every version up to 1.86-1: fixed in 1.86-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 108 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 8 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-22 02:26 UTCOSV refresh
  2. 2026-11-21 16:41 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-11-20 16:38 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  4. 2026-11-20 01:39 UTCEchelonGraph re-scored
  5. 2026-11-20 01:39 UTCVendor advisory
  6. 2026-11-20 01:39 UTCGHSA enrichmentGHSA-hqqj-v58h-gr7x · GitHub severity HIGH
  7. 2026-11-19 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-11-18 20:23 UTCEchelonGraph re-scored
  9. 2026-11-18 20:23 UTCVendor advisory
  10. 2026-11-18 20:23 UTCGHSA enrichmentGHSA-hqqj-v58h-gr7x · GitHub severity HIGH
  11. 2026-11-18 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-11-17 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  13. 2026-11-16 16:52 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-11-15 17:02 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  15. 2026-11-14 16:41 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-11-13 16:57 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-11-11 03:56 UTCEchelonGraph re-scored
  20. 2026-11-11 03:56 UTCVendor advisory
  21. 2026-11-11 03:56 UTCGHSA enrichmentGHSA-hqqj-v58h-gr7x · GitHub severity HIGH
  22. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  23. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  25. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.2% · 5th percentile
Show 75 more
  1. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-11-03 20:19 UTCEchelonGraph re-scored
  5. 2026-11-03 20:19 UTCVendor advisory
  6. 2026-11-03 20:19 UTCGHSA enrichmentGHSA-hqqj-v58h-gr7x · GitHub severity HIGH
  7. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  13. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-10-27 21:08 UTCEchelonGraph re-scored
  15. 2026-10-27 21:08 UTCVendor advisory
  16. 2026-10-27 21:08 UTCGHSA enrichmentGHSA-hqqj-v58h-gr7x · GitHub severity HIGH
  17. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  18. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-10-25 14:07 UTCEchelonGraph re-scored
  21. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  22. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  23. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  25. 2026-10-20 18:36 UTCEchelonGraph re-scored
  26. 2026-10-20 18:36 UTCVendor advisory
  27. 2026-10-20 18:36 UTCGHSA enrichmentGHSA-hqqj-v58h-gr7x · GitHub severity HIGH
  28. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  29. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  30. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  31. 2026-10-18 03:16 UTCEchelonGraph re-scored
  32. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  33. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  34. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  35. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  36. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  37. 2026-10-13 08:24 UTCEchelonGraph re-scored
  38. 2026-10-13 08:24 UTCGHSA enrichmentGHSA-hqqj-v58h-gr7x · GitHub severity HIGH
  39. 2026-10-12 15:42 UTCEchelonGraph re-scored
  40. 2026-10-11 19:59 UTCGHSA enrichmentGHSA-hqqj-v58h-gr7x · GitHub severity HIGH
  41. 2026-10-11 19:28 UTCEchelonGraph re-scored
  42. 2026-10-11 16:43 UTCEchelonGraph re-scored
  43. 2026-10-11 14:03 UTCEchelonGraph re-scored
  44. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  45. 2026-10-11 08:42 UTCGHSA enrichmentGHSA-hqqj-v58h-gr7x · GitHub severity HIGH
  46. 2026-10-10 21:26 UTCEchelonGraph re-scored
  47. 2026-10-10 21:25 UTCGHSA enrichmentGHSA-hqqj-v58h-gr7x · GitHub severity HIGH
  48. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  49. 2026-10-10 10:06 UTCGHSA enrichmentGHSA-hqqj-v58h-gr7x · GitHub severity HIGH
  50. 2026-10-09 22:50 UTCEchelonGraph re-scored
  51. 2026-10-09 22:50 UTCGHSA enrichmentGHSA-hqqj-v58h-gr7x · GitHub severity HIGH
  52. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  53. 2026-10-09 11:34 UTCGHSA enrichmentGHSA-hqqj-v58h-gr7x · GitHub severity HIGH
  54. 2026-10-08 23:19 UTCEchelonGraph re-scored
  55. 2026-10-08 23:19 UTCGHSA enrichmentGHSA-hqqj-v58h-gr7x · GitHub severity HIGH
  56. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  57. 2026-10-08 12:04 UTCGHSA enrichmentGHSA-hqqj-v58h-gr7x · GitHub severity HIGH
  58. 2026-10-08 00:48 UTCEchelonGraph re-scored
  59. 2026-10-08 00:48 UTCGHSA enrichmentGHSA-hqqj-v58h-gr7x · GitHub severity HIGH
  60. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  61. 2026-10-07 13:32 UTCGHSA enrichmentGHSA-hqqj-v58h-gr7x · GitHub severity HIGH
  62. 2026-10-07 02:08 UTCEchelonGraph re-scored
  63. 2026-10-07 02:08 UTCGHSA enrichmentGHSA-hqqj-v58h-gr7x · GitHub severity HIGH
  64. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  65. 2026-10-06 14:52 UTCGHSA enrichmentGHSA-hqqj-v58h-gr7x · GitHub severity HIGH
  66. 2026-10-06 04:44 UTCEchelonGraph re-scored
  67. 2026-10-06 04:44 UTCGHSA enrichmentGHSA-hqqj-v58h-gr7x · GitHub severity HIGH
  68. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  69. 2026-10-05 17:29 UTCEchelonGraph re-scored
  70. 2026-10-05 17:29 UTCGHSA enrichmentGHSA-hqqj-v58h-gr7x · GitHub severity HIGH
  71. 2026-10-05 17:07 UTCEchelonGraph re-scored
  72. 2026-10-05 17:07 UTCGHSA enrichmentGHSA-hqqj-v58h-gr7x · GitHub severity HIGH
  73. 2026-10-05 06:33 UTCEchelonGraph re-scored
  74. 2026-10-05 06:33 UTCGHSA enrichmentGHSA-hqqj-v58h-gr7x · GitHub severity HIGH
  75. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 5th percentile

Frequently asked(5)

What is CVE-2026-71889?
CVE-2026-71889 is a high-severity vulnerability; its CVE record was published on October 3, 2026. 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…
When was the CVE record for CVE-2026-71889 published?
The CVE record for CVE-2026-71889 was published on October 3, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 6, 2026; the record at its source may have been updated since.
Is CVE-2026-71889 actively exploited?
CVE-2026-71889 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-71889?
CVE-2026-71889 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-71889?
A fix for CVE-2026-71889 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-71889 are linked in the Vendor and National Authority Advisories panel on this page. NCSC-NL's advisory for CVE-2026-71889 is also listed there, in Dutch, as NCSC-NL published it; not translated.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-71889

Explore →

Is Your Infrastructure Affected by CVE-2026-71889?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.