CVE-2026-13505

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (15th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In Bouncy Castle for Java FIPS (BC-FJA) before bc-fips 1.0.2.7 (1.0.X series), 2.0.2 (2.0.X series) and 2.1.3 (2.1.X series), sensitive key material held by the AES and DESede engines, the SP 800-90A DRBGs, SymmetricSecretKey and the PBKD and scrypt parameter classes was zeroised on garbage collection by overriding Object.finalize. Finalization runs at an unspecified time and in an unspecified order and is serviced by a single finalizer thread, so where objects carrying a finalizer are allocated faster than that thread retires them the pending-finalization queue grows without bound: disposal falls arbitrarily far behind, which can contribute to an OutOfMemoryError under load, and the key material those objects hold stays resident in the heap for as long as they are queued, defeating the purpose of the zeroisation. The behaviour was not a problem on Java 8 or Java 11; it is later JVMs, on which finalization has been deprecated and progressively de-emphasised, where it becomes one. Disposal of these classes now runs from a java.lang.ref.Cleaner registered in the multi-release jdk1.9 overlay, so on Java 9 and later it no longer depends on the finalizer being scheduled. Bouncy Castle for Java (bcprov) and Bouncy Castle for Java LTS are not affected, as neither implements the finalizer-based zeroisation scheme.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
54
EG Risk 54/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity87% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
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.3%
EPSS %ILE
15th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 8, 2026

Last Modified

September 3, 2026

Advisory Details (1)

Auto-updated Aug 8, 2026
Patch available.
generic

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

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

Vendor Advisories for CVE-2026-13505(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.bouncycastle:bc-fips2.1.0, 2.1.1, 2.1.2
  • every version up to 1.0.2.7: fixed in 1.0.2.7
  • 2.0.0 up to 2.0.2: fixed in 2.0.2
  • 2.1.0 up to 2.1.3: fixed in 2.1.3
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 67× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 170 total refreshes for this CVE.

  1. 2026-10-04 23:21 UTCEPSS rescore
  2. 2026-10-04 05:41 UTCEG score recompute
  3. 2026-10-03 14:25 UTCEPSS rescore
  4. 2026-10-03 00:59 UTCEG score recompute
  5. 2026-10-02 09:29 UTCEG score recompute
  6. 2026-10-01 19:49 UTCEPSS rescore
  7. 2026-09-30 22:54 UTCEG score recompute
  8. 2026-09-30 15:02 UTCEPSS rescore
  9. 2026-09-29 15:20 UTCEPSS rescore
  10. 2026-09-29 05:41 UTCEG score recompute
  11. 2026-09-28 13:51 UTCEPSS rescore
  12. 2026-09-27 17:06 UTCEG score recompute
  13. 2026-09-26 15:58 UTCEPSS rescore
  14. 2026-09-25 04:12 UTCEG score recompute
  15. 2026-09-23 15:09 UTCEG score recompute
  16. 2026-09-23 13:47 UTCEPSS rescore
  17. 2026-09-23 02:19 UTCEG score recompute
  18. 2026-09-22 00:39 UTCEG score recompute
  19. 2026-09-21 11:33 UTCEG score recompute
  20. 2026-09-20 20:15 UTCEPSS rescore
  21. 2026-09-19 20:10 UTCEG score recompute
  22. 2026-09-19 06:40 UTCEG score recompute
  23. 2026-09-18 19:27 UTCEPSS rescore
  24. 2026-09-18 17:32 UTCGHSA enrichment
  25. 2026-09-18 03:59 UTCEG score recompute
Show 75 more
  1. 2026-09-18 03:59 UTCGHSA enrichment
  2. 2026-09-17 15:10 UTCGHSA enrichment
  3. 2026-09-17 00:53 UTCEG score recompute
  4. 2026-09-17 00:53 UTCGHSA enrichment
  5. 2026-09-16 06:11 UTCEG score recompute
  6. 2026-09-16 06:11 UTCGHSA enrichment
  7. 2026-09-16 05:14 UTCEPSS rescore
  8. 2026-09-15 17:21 UTCGHSA enrichment
  9. 2026-09-15 04:29 UTCEG score recompute
  10. 2026-09-15 04:29 UTCGHSA enrichment
  11. 2026-09-14 15:28 UTCGHSA enrichment
  12. 2026-09-14 02:33 UTCEG score recompute
  13. 2026-09-14 02:33 UTCGHSA enrichment
  14. 2026-09-13 16:46 UTCEPSS rescore
  15. 2026-09-13 13:44 UTCGHSA enrichment
  16. 2026-09-13 00:55 UTCEG score recompute
  17. 2026-09-13 00:55 UTCGHSA enrichment
  18. 2026-09-12 15:00 UTCEPSS rescore
  19. 2026-09-12 11:55 UTCGHSA enrichment
  20. 2026-09-11 22:09 UTCEG score recompute
  21. 2026-09-11 22:09 UTCGHSA enrichment
  22. 2026-09-11 14:52 UTCEPSS rescore
  23. 2026-09-11 09:36 UTCEPSS rescore
  24. 2026-09-11 09:19 UTCGHSA enrichment
  25. 2026-09-10 20:30 UTCEG score recompute
  26. 2026-09-10 20:30 UTCGHSA enrichment
  27. 2026-09-10 09:34 UTCEPSS rescore
  28. 2026-09-10 07:37 UTCGHSA enrichment
  29. 2026-09-09 18:48 UTCGHSA enrichment
  30. 2026-09-09 05:59 UTCEG score recompute
  31. 2026-09-09 05:59 UTCGHSA enrichment
  32. 2026-09-08 22:00 UTCEPSS rescore
  33. 2026-09-08 07:26 UTCGHSA enrichment
  34. 2026-09-07 17:41 UTCEG score recompute
  35. 2026-09-07 17:41 UTCGHSA enrichment
  36. 2026-09-07 16:01 UTCEPSS rescore
  37. 2026-09-06 17:46 UTCEG score recompute
  38. 2026-09-06 17:46 UTCGHSA enrichment
  39. 2026-09-06 13:47 UTCEPSS rescore
  40. 2026-09-06 04:56 UTCGHSA enrichment
  41. 2026-09-05 16:08 UTCEG score recompute
  42. 2026-09-05 16:08 UTCGHSA enrichment
  43. 2026-09-05 02:20 UTCEG score recompute
  44. 2026-09-05 02:20 UTCGHSA enrichment
  45. 2026-09-04 08:49 UTCEG score recompute
  46. 2026-09-04 08:49 UTCGHSA enrichment
  47. 2026-09-04 05:06 UTCEPSS rescore
  48. 2026-09-03 16:57 UTCGHSA enrichment
  49. 2026-09-03 03:59 UTCEG score recompute
  50. 2026-09-03 03:59 UTCGHSA enrichment
  51. 2026-09-02 14:11 UTCEPSS rescore
  52. 2026-09-02 06:42 UTCGHSA enrichment
  53. 2026-09-01 17:37 UTCEG score recompute
  54. 2026-09-01 17:37 UTCGHSA enrichment
  55. 2026-09-01 13:53 UTCEPSS rescore
  56. 2026-09-01 04:39 UTCEPSS rescore
  57. 2026-08-31 22:26 UTCGHSA enrichment
  58. 2026-08-31 00:47 UTCEG score recompute
  59. 2026-08-31 00:47 UTCGHSA enrichment
  60. 2026-08-30 19:17 UTCEPSS rescore
  61. 2026-08-30 11:58 UTCEG score recompute
  62. 2026-08-30 11:58 UTCGHSA enrichment
  63. 2026-08-30 01:21 UTCEPSS rescore
  64. 2026-08-29 23:09 UTCGHSA enrichment
  65. 2026-08-29 10:20 UTCEG score recompute
  66. 2026-08-29 10:20 UTCGHSA enrichment
  67. 2026-08-28 21:40 UTCEPSS rescore
  68. 2026-08-28 13:44 UTCGHSA enrichment
  69. 2026-08-28 00:54 UTCEG score recompute
  70. 2026-08-28 00:54 UTCGHSA enrichment
  71. 2026-08-27 14:24 UTCEPSS rescore
  72. 2026-08-27 11:40 UTCGHSA enrichment
  73. 2026-08-26 22:51 UTCEG score recompute
  74. 2026-08-26 22:51 UTCGHSA enrichment
  75. 2026-08-26 10:02 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-13505?
CVE-2026-13505 is a high vulnerability published on August 8, 2026. In Bouncy Castle for Java FIPS (BC-FJA) before bc-fips 1.0.2.7 (1.0.X series), 2.0.2 (2.0.X series) and 2.1.3 (2.1.X series), sensitive key material held by the AES and DESede engines, the SP 800-90A DRBGs, SymmetricSecretKey and the PBKD and scrypt parameter classes was zeroised on garbage…
When was CVE-2026-13505 disclosed?
CVE-2026-13505 was first published on August 8, 2026, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13505 actively exploited?
CVE-2026-13505 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-13505?
CVE-2026-13505 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-13505?
A fix for CVE-2026-13505 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-13505 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-13505

Explore →

Is Your Infrastructure Affected by CVE-2026-13505?

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

Book a Demo →Browse All CVEs