CVE-2026-17508

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (36th 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 — 3 sources updated this week

Also known asEUVD-2026-91236 (ENISA EUVD) · GHSA-m3x3-p27c-whhp (GitHub Security Advisories)Source: ENISA EUVD

5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In Bouncy Castle for Java before 1.86, several password-based key derivation entry points ran the KDF with cost parameters taken from the untrusted input being processed, without bounding them, so a small input could dictate an arbitrary amount of work before any password or integrity check could reject it. The affected paths are the RFC 9579 PBMAC1 MAC calculator builders, which took the PBKDF2 iteration count and derived-key length straight out of PBMAC1Params (JcePBMac1CalculatorBuilder, and PKCS12PBEUtils.createPBMac1Calculator reached from PKCS12PfxPdu.isMacValid); the scrypt parallelization parameter p in the PKCS#8 and PKCS#12 cost guards, which bounded only the cost parameter N and the block size r even though the scratch buffer scales with r times p, so the configured memory ceiling could be evaded entirely; the raw JCA PBKDF2 provider (org.bouncycastle.jcajce.provider.symmetric.PBEPBKDF2); and the bcrypt round count read from an encrypted OpenSSH v1 private key's own kdfoptions. Each now bounds the parameter before deriving, in line with the caps already applied elsewhere in the tree, with the OpenSSH round count configurable through the new org.bouncycastle.openssh.max_rounds property. This completes the bounding begun in 1.85 for the PKCS#8 / PBES2 decryptors (CVE-2026-15055). 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).

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
24
EG Risk 24/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)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.4%
EPSS %ILE
36th
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 (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 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.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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 2, 2026

Last Modified

October 2, 2026

Advisory Details (7)

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

commit 480d878aa6f7 (bcgit/bc-java)

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

https://github.com/bcgit/bc-java/commit/480d878aa6f7dc8b20403064f304bbe0decbbb1a
GitHub commit

commit e72bc0681ff4 (bcgit/bc-java)

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

https://github.com/bcgit/bc-java/commit/e72bc0681ff4227fced912ef7394daf7b7d57bb3
GitHub commit

commit 766a31026ac2 (bcgit/bc-java)

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

https://github.com/bcgit/bc-java/commit/766a31026ac24ed3c6cad8662058ba450c338da1
GitHub commit

commit 20ed9e203cae (bcgit/bc-java)

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

https://github.com/bcgit/bc-java/commit/20ed9e203caec91d25cd386ceb6d364e9b068f67
GitHub commit

commit 442393bf187c (bcgit/bc-java)

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

https://github.com/bcgit/bc-java/commit/442393bf187c914b1e66fbed4fab532a1fe06c6a
GitHub commit

commit 882fdab53f6c (bcgit/bc-java)

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

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

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

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

Vendor Advisories for CVE-2026-17508(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)
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 9× in last 7d / 55× 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.

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. 2 repeat rows among the latest 65 are merged into the row they repeat.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  3. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  4. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  5. 2026-10-29 15:59 UTCEG score recompute
  6. 2026-10-29 15:59 UTCGHSA enrichmentGHSA-m3x3-p27c-whhp
  7. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  8. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  9. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  10. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  11. 2026-10-25 14:46 UTCEG score recompute
  12. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  13. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  14. 2026-10-23 06:18 UTCEG score recompute
  15. 2026-10-23 06:17 UTCGHSA enrichmentGHSA-m3x3-p27c-whhp
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  17. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  18. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  21. 2026-10-18 04:00 UTCEG score recompute
  22. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  23. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  24. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  25. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
Show 38 more
  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  3. 2026-10-12 16:28 UTCEG score recompute
  4. 2026-10-12 01:18 UTCGHSA enrichmentGHSA-m3x3-p27c-whhp
  5. 2026-10-11 20:08 UTCEG score recompute
  6. 2026-10-11 17:21 UTCEG score recompute
  7. 2026-10-11 14:53 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  9. 2026-10-11 00:32 UTCEG score recompute
  10. 2026-10-11 00:32 UTCGHSA enrichmentGHSA-m3x3-p27c-whhp
  11. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  12. 2026-10-09 23:43 UTCEG score recompute
  13. 2026-10-09 23:43 UTCGHSA enrichmentGHSA-m3x3-p27c-whhp
  14. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  15. 2026-10-08 22:58 UTCEG score recompute
  16. 2026-10-08 22:57 UTCGHSA enrichmentGHSA-m3x3-p27c-whhp
  17. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  18. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  19. 2026-10-07 22:11 UTCGHSA enrichmentGHSA-m3x3-p27c-whhp
  20. 2026-10-06 21:25 UTCEG score recompute
  21. 2026-10-06 21:25 UTCGHSA enrichmentGHSA-m3x3-p27c-whhp
  22. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  23. 2026-10-05 20:39 UTCEG score recompute
  24. 2026-10-05 20:39 UTCGHSA enrichmentGHSA-m3x3-p27c-whhp
  25. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  26. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  27. 2026-10-04 19:53 UTCGHSA enrichmentGHSA-m3x3-p27c-whhp
  28. 2026-10-03 19:06 UTCEG score recompute
  29. 2026-10-03 19:06 UTCGHSA enrichmentGHSA-m3x3-p27c-whhp
  30. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  31. 2026-10-02 18:20 UTCEG score recompute
  32. 2026-10-02 18:20 UTCGHSA enrichmentGHSA-m3x3-p27c-whhp
  33. 2026-10-02 17:47 UTCEG score recompute
  34. 2026-10-02 17:47 UTCGHSA enrichmentGHSA-m3x3-p27c-whhp
  35. 2026-10-02 14:45 UTCGHSA enrichmentGHSA-m3x3-p27c-whhp
  36. 2026-10-02 08:27 UTCEG score recompute
  37. 2026-10-02 07:47 UTCEG score recomputeFirst assessed: 5.3 MEDIUM
  38. 2026-10-02 07:45 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-17508?
CVE-2026-17508 is a medium-severity vulnerability; its CVE record was published on October 2, 2026. In Bouncy Castle for Java before 1.86, several password-based key derivation entry points ran the KDF with cost parameters taken from the untrusted input being processed, without bounding them, so a small input could dictate an arbitrary amount of work before any password or integrity check could…
When was the CVE record for CVE-2026-17508 published?
The CVE record for CVE-2026-17508 was published on October 2, 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 2, 2026; the record at its source may have been updated since.
Is CVE-2026-17508 actively exploited?
CVE-2026-17508 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-17508?
CVE-2026-17508 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-17508?
A fix for CVE-2026-17508 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-17508 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-17508?

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

Book a Demo →Browse All CVEs