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).
CVE-2026-71888
“—” 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.
Also known asEUVD-2026-91991 (ENISA EUVD) · GHSA-j453-27jp-4cph (GitHub Security Advisories)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.7
- EG Score
- 8.7HIGHmedium confidence
- EG Risk
- 54EG 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 · CVSS v3.0 or v3.1
- EG Likelihood
- 0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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, 2026commit dcb683b32b44 (bcgit/bc-java)
Fix landed in bcgit/bc-java commit dcb683b32b44 — awaiting tagged release
https://github.com/bcgit/bc-java/commit/dcb683b32b440f1beb1d2276a34930164281fb95CVE‐2026‐71888 · bcgit/bc-java Wiki · GitHub
https://github.com/bcgit/bc-java/wiki/CVE%E2%80%902026%E2%80%9071888Vendor Advisories for CVE-2026-71888(12)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:88159Red Hat Product SecurityCritical
Red Hat Security Advisory: Release of Red Hat OpenShift Developer Tools - Openshift Jenkins 4.17 security update.
- RHSA-2026:88158Red Hat Product SecurityCritical
Red Hat Security Advisory: Release of Red Hat OpenShift Developer Tools - Openshift Jenkins 4.19 security update.
- RHSA-2026:88157Red Hat Product SecurityCritical
Red Hat Security Advisory: Release of Red Hat OpenShift Developer Tools - Openshift Jenkins 4.20 security update.
- RHSA-2026:88156Red Hat Product SecurityCritical
Red Hat Security Advisory: Release of Red Hat OpenShift Developer Tools - Openshift Jenkins 4.16 security update.
- RHSA-2026:88155Red Hat Product SecurityCritical
Red Hat Security Advisory: Release of Red Hat OpenShift Developer Tools - Openshift Jenkins 4.21 security update.
- RHSA-2026:88154Red Hat Product SecurityCritical
Red Hat Security Advisory: Release of Red Hat OpenShift Developer Tools - Openshift Jenkins 4.22 security update.
- RHSA-2026:88153Red Hat Product SecurityCritical
Red Hat Security Advisory: Release of Red Hat OpenShift Developer Tools - Openshift Jenkins 4.18 security update.
- RHSA-2026:88151Red Hat Product SecurityCritical
Red Hat Security Advisory: Release of Red Hat OpenShift Developer Tools - Openshift Jenkins 4.14 security update.
- +4 more
Patch Availability(11)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | ocp-tools-4/jenkins-rhel8:1792044386 | 2026-10-22 | redhat |
| redhat | ocp-tools-4/jenkins-rhel8:1792044382 | 2026-10-22 | redhat |
| redhat | ocp-tools-4/jenkins-rhel9:1792040096 | 2026-10-22 | redhat |
| redhat | ocp-tools-4/jenkins-rhel9:1792040287 | 2026-10-22 | redhat |
| redhat | ocp-tools-4/jenkins-rhel9:1792040428 | 2026-10-22 | redhat |
| redhat | ocp-tools-4/jenkins-rhel9:1792040131 | 2026-10-22 | redhat |
| redhat | ocp-tools-4/jenkins-rhel9:1792041514 | 2026-10-22 | redhat |
| redhat | ocp-tools-4/jenkins-rhel9:1792040733 | 2026-10-22 | redhat |
| redhat | ocp-tools-4/jenkins-rhel9:1792040081 | 2026-10-22 | redhat |
| redhat | ocp-tools-4/jenkins-rhel8:1792044327 | 2026-10-22 | redhat |
| redhat | ocp-tools-4/jenkins-rhel8:1792044326 | 2026-10-22 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(3 across 3 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| bouncycastle | 1.72-2 ... 1.86-1 (6 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| bouncycastle | 1.80-3, 1.86-1 |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| bouncycastle | 1.80-3 |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 67× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.
- 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-27 21:08 UTCEG score recompute
- 2026-10-27 21:08 UTCVendor advisory
- 2026-10-27 21:08 UTCGHSA enrichmentGHSA-j453-27jp-4cph · GitHub severity HIGH
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-25 14:07 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-20 18:36 UTCEG score recompute
- 2026-10-20 18:36 UTCGHSA enrichmentGHSA-j453-27jp-4cph · GitHub severity HIGH
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-18 03:16 UTCEG score recompute
- 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-13 08:24 UTCEG score recompute
- 2026-10-13 08:24 UTCGHSA enrichmentGHSA-j453-27jp-4cph · GitHub severity HIGH
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
Show 45 moreShow fewer
- 2026-10-12 15:42 UTCEG score recompute
- 2026-10-11 20:32 UTCGHSA enrichmentGHSA-j453-27jp-4cph · GitHub severity HIGH
- 2026-10-11 19:28 UTCEG score recompute
- 2026-10-11 16:43 UTCEG score recompute
- 2026-10-11 14:03 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-11 09:07 UTCGHSA enrichmentGHSA-j453-27jp-4cph · GitHub severity HIGH
- 2026-10-10 21:43 UTCEG score recompute
- 2026-10-10 21:42 UTCGHSA enrichmentGHSA-j453-27jp-4cph · GitHub severity HIGH
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-10 10:18 UTCGHSA enrichmentGHSA-j453-27jp-4cph · GitHub severity HIGH
- 2026-10-09 22:57 UTCEG score recompute
- 2026-10-09 22:57 UTCGHSA enrichmentGHSA-j453-27jp-4cph · GitHub severity HIGH
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-09 11:34 UTCGHSA enrichmentGHSA-j453-27jp-4cph · GitHub severity HIGH
- 2026-10-08 23:45 UTCEG score recompute
- 2026-10-08 23:45 UTCGHSA enrichmentGHSA-j453-27jp-4cph · GitHub severity HIGH
- 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-08 12:24 UTCGHSA enrichmentGHSA-j453-27jp-4cph · GitHub severity HIGH
- 2026-10-08 00:55 UTCEG score recompute
- 2026-10-08 00:55 UTCGHSA enrichmentGHSA-j453-27jp-4cph · GitHub severity HIGH
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-07 13:34 UTCGHSA enrichmentGHSA-j453-27jp-4cph · GitHub severity HIGH
- 2026-10-07 02:13 UTCEG score recompute
- 2026-10-07 02:13 UTCGHSA enrichmentGHSA-j453-27jp-4cph · GitHub severity HIGH
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-06 14:52 UTCGHSA enrichmentGHSA-j453-27jp-4cph · GitHub severity HIGH
- 2026-10-06 04:49 UTCEG score recompute
- 2026-10-06 04:49 UTCGHSA enrichmentGHSA-j453-27jp-4cph · GitHub severity HIGH
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-05 17:29 UTCEG score recompute
- 2026-10-05 17:29 UTCGHSA enrichmentGHSA-j453-27jp-4cph · GitHub severity HIGH
- 2026-10-05 16:58 UTCEG score recompute
- 2026-10-05 16:58 UTCGHSA enrichmentGHSA-j453-27jp-4cph · GitHub severity HIGH
- 2026-10-05 06:49 UTCEG score recompute
- 2026-10-05 06:49 UTCGHSA enrichmentGHSA-j453-27jp-4cph · GitHub severity HIGH
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-04 19:28 UTCGHSA enrichmentGHSA-j453-27jp-4cph · GitHub severity HIGH
- 2026-10-04 08:07 UTCGHSA enrichmentGHSA-j453-27jp-4cph · GitHub severity HIGH
- 2026-10-03 20:46 UTCEG score recompute
- 2026-10-03 20:46 UTCGHSA enrichmentGHSA-j453-27jp-4cph · GitHub severity HIGH
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-03 09:25 UTCEG score recompute
- 2026-10-03 08:46 UTCEG score recomputeFirst assessed: 8.7 HIGH
- 2026-10-03 08:44 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownDebian:12:bouncycastle
Same vendor
10 shownredhat:RHSA-2026:88149
Frequently asked(5)
What is CVE-2026-71888?
When was the CVE record for CVE-2026-71888 published?
Is CVE-2026-71888 actively exploited?
What is the CVSS score of CVE-2026-71888?
How do I remediate CVE-2026-71888?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-71888
Is Your Infrastructure Affected by CVE-2026-71888?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.