In Bouncy Castle for Java before 1.86, the opt-in key-size validation on CMS key-transport recipients, org.bouncycastle.cms.jcajce.JceKeyTransRecipient.setKeySizeValidation(true), never ran for a message using RFC 9709 content-encryption key derivation (id-alg-cek-hkdf-sha256). The branch that should have selected the actual content-encryption algorithm carried in the key derivation AlgorithmIdentifier's parameters compared the encrypted-key byte array against the id-alg-cek-hkdf-sha256 object identifier, a comparison between a byte array and an ASN1ObjectIdentifier that is false for every possible input, so the check fell through to a key-size lookup on the outer wrapper OID. That OID identifies a key-derivation construction rather than a cipher and has no registered key size, so the size comparison was skipped entirely. A key-transport EnvelopedData or AuthEnvelopedData whose transported, HKDF-derived content-encryption key did not match the key size of the advertised content-encryption algorithm was therefore accepted even with validation explicitly enabled, silently defeating the only mechanism the API offers for enforcing recovered key size. The recipient now dispatches on the content-encryption AlgorithmIdentifier's algorithm OID, so validation checks the recovered key against the inner content-encryption algorithm. Messages with a matching key size, non-HKDF messages, and recipients that do not enable validation are unaffected. This issue also affects Bouncy Castle for Java FIPS (BC-FJA) before bcpkix-fips 2.0.13 (2.0.X series) and 2.1.13 (2.1.X series).
CVE-2026-71892
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (6th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-91989 (ENISA EUVD) · GHSA-x42w-4gqh-qrvm (GitHub Security Advisories)Source: ENISA EUVD
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 6.9
- EG Score
- 6.9MEDIUMmedium confidence
- EG Risk
- 46EG Risk 46/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)Severity69% × 45%Impact severity (EG Severity): CVSS 6.9 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
- 6th
- 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 (6.9): severity, escalated by confirmed exploitation. This CVE's 6.9 is its impact severity (EG Severity), not escalated.
- EG Severity
- 6.9 MEDIUMCVSS-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.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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 be0a7d925c81 (bcgit/bc-java)
Fix landed in bcgit/bc-java commit be0a7d925c81 — awaiting tagged release
https://github.com/bcgit/bc-java/commit/be0a7d925c818ef2f338bcec55178b9b6336dfc3CVE‐2026‐71892 · bcgit/bc-java Wiki · GitHub
https://github.com/bcgit/bc-java/wiki/CVE%E2%80%902026%E2%80%9071892Vendor Advisories for CVE-2026-71892(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
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 9× in last 7d / 56× 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-02 16:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-29 16:58 UTCEG score recompute
- 2026-10-29 16:58 UTCGHSA enrichmentGHSA-x42w-4gqh-qrvm
- 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-25 14:07 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-22 19:23 UTCEG score recompute
- 2026-10-22 19:23 UTCGHSA enrichmentGHSA-x42w-4gqh-qrvm
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-18 03:16 UTCEG score recompute
- 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
Show 37 moreShow fewer
- 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-12 15:42 UTCEG score recompute
- 2026-10-11 19:49 UTCGHSA enrichmentGHSA-x42w-4gqh-qrvm
- 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.2% · 6th percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-10 18:53 UTCEG score recompute
- 2026-10-10 18:53 UTCGHSA enrichmentGHSA-x42w-4gqh-qrvm
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-09 17:56 UTCEG score recompute
- 2026-10-09 17:56 UTCGHSA enrichmentGHSA-x42w-4gqh-qrvm
- 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-08 17:00 UTCEG score recompute
- 2026-10-08 17:00 UTCGHSA enrichmentGHSA-x42w-4gqh-qrvm
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-07 16:04 UTCEG score recompute
- 2026-10-07 16:04 UTCGHSA enrichmentGHSA-x42w-4gqh-qrvm
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-06 14:52 UTCEG score recompute
- 2026-10-06 14:52 UTCGHSA enrichmentGHSA-x42w-4gqh-qrvm
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-05 17:29 UTCEG score recompute
- 2026-10-05 17:29 UTCGHSA enrichmentGHSA-x42w-4gqh-qrvm
- 2026-10-05 17:07 UTCEG score recompute
- 2026-10-05 17:07 UTCGHSA enrichmentGHSA-x42w-4gqh-qrvm
- 2026-10-05 11:17 UTCEG score recompute
- 2026-10-05 11:17 UTCGHSA enrichmentGHSA-x42w-4gqh-qrvm
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-04 10:21 UTCEG score recompute
- 2026-10-04 10:21 UTCGHSA enrichmentGHSA-x42w-4gqh-qrvm
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-03 09:25 UTCEG score recompute
- 2026-10-03 08:46 UTCEG score recomputeFirst assessed: 6.9 MEDIUM
- 2026-10-03 08:44 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownDebian:12:bouncycastle
Frequently asked(5)
What is CVE-2026-71892?
When was the CVE record for CVE-2026-71892 published?
Is CVE-2026-71892 actively exploited?
What is the CVSS score of CVE-2026-71892?
How do I remediate CVE-2026-71892?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-71892
Is Your Infrastructure Affected by CVE-2026-71892?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.