CVE-2026-71888

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.1% (1st 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-91991 (ENISA EUVD) · GHSA-j453-27jp-4cph (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.1%CVSS: 8.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In Bouncy Castle for Java before 1.86, the streaming CMS AuthenticatedData parser accepted a message whose digestAlgorithm and authAttrs fields disagreed about whether authenticated attributes were present. RFC 5652 sec. 9.1 pairs the two, requiring that authAttrs be present whenever digestAlgorithm is, and sec. 9.2 makes the MAC cover the DER encoding of authAttrs when they are present and the eContent OCTET STRING directly when they are not. CMSAuthenticatedDataParser has to choose between those two in its constructor, before it can reach authAttrs, which comes later in the SEQUENCE, so it chose on digestAlgorithm alone: for a message with digestAlgorithm absent but authAttrs present it verified the content MAC and then returned the attributes through getAuthAttrs() as though they had been authenticated, when the MAC had never covered them. An attacker able to modify a message in transit could insert an authenticated attribute, such as an RFC 2634 ESSSecurityLabel, into an otherwise valid message while holding neither the key-encryption key nor the content-MAC key, and an application taking an authorization, routing or labelling decision from those attributes would act on attacker-chosen values. The content itself remained MAC-bound. asn1.cms.AuthenticatedData now rejects the mismatched pairing when parsing and CMSAuthenticatedDataParser cross-checks the two fields once authAttrs is read. This is a variant of CVE-2026-59642, which bound the content to the MAC for messages that legitimately carry authAttrs, and which does not address this case. This issue also affects Bouncy Castle for Java LTS before 2.73.13, and 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), and bcutil-fips 2.0.8 (2.0.X series) and 2.1.8 (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.1% × 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.1%
EPSS %ILE
1st
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.1% 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 dcb683b32b44 (bcgit/bc-java)

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

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

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

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

Vendor and National Authority Advisories for CVE-2026-71888(14)

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(12)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-modelmesh-rhel9:17933407462026-11-19redhat
redhatocp-tools-4/jenkins-rhel8:17920443822026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920400962026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920402872026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920404282026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920401312026-10-22redhat
redhatocp-tools-4/jenkins-rhel8:17920443862026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920407332026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920400812026-10-22redhat
redhatocp-tools-4/jenkins-rhel8:17920443272026-10-22redhat
redhatocp-tools-4/jenkins-rhel8:17920443262026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920415142026-10-22redhat

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

Frequently asked(5)

What is CVE-2026-71888?
CVE-2026-71888 is a high-severity vulnerability; its CVE record was published on October 3, 2026. In Bouncy Castle for Java before 1.86, the streaming CMS AuthenticatedData parser accepted a message whose digestAlgorithm and authAttrs fields disagreed about whether authenticated attributes were present. RFC 5652 sec. 9.1 pairs the two, requiring that authAttrs be present whenever…
When was the CVE record for CVE-2026-71888 published?
The CVE record for CVE-2026-71888 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-71888 actively exploited?
CVE-2026-71888 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-71888?
CVE-2026-71888 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-71888?
A fix for CVE-2026-71888 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-71888 are linked in the Vendor and National Authority Advisories panel on this page. NCSC-NL's advisory for CVE-2026-71888 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-71888

Explore →

Is Your Infrastructure Affected by CVE-2026-71888?

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