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%, top 83% of all CVEs by exploit prediction. 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
Trending — 3 sources updated this week
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%CVSS: 8.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.7(medium)
EG Risk
54(Track)
EG Risk 54/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

August 8, 2026

Last Modified

August 10, 2026

Advisory Details (1)

Auto-updated Aug 8, 2026
No patch confirmed yet.
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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 26× in last 7d / 51× 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.

  1. 2026-08-20 12:07 UTCGHSA enrichment
  2. 2026-08-19 23:18 UTCEG score recompute
  3. 2026-08-19 23:18 UTCGHSA enrichment
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-19 10:29 UTCGHSA enrichment
  6. 2026-08-18 21:41 UTCEG score recompute
  7. 2026-08-18 21:40 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-18 08:23 UTCGHSA enrichment
  10. 2026-08-17 19:24 UTCEG score recompute
  11. 2026-08-17 19:24 UTCGHSA enrichment
  12. 2026-08-17 05:44 UTCGHSA enrichment
  13. 2026-08-16 16:23 UTCEG score recompute
  14. 2026-08-16 16:23 UTCGHSA enrichment
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 03:35 UTCEG score recompute
  17. 2026-08-16 03:35 UTCGHSA enrichment
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 14:47 UTCGHSA enrichment
  20. 2026-08-15 01:58 UTCEG score recompute
  21. 2026-08-15 01:58 UTCGHSA enrichment
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-14 13:09 UTCGHSA enrichment
  24. 2026-08-14 00:21 UTCEG score recompute
  25. 2026-08-14 00:21 UTCGHSA enrichment
Show 26 more
  1. 2026-08-13 22:00 UTCEPSS rescore
  2. 2026-08-13 11:32 UTCGHSA enrichment
  3. 2026-08-12 22:44 UTCEG score recompute
  4. 2026-08-12 22:44 UTCGHSA enrichment
  5. 2026-08-12 13:50 UTCEPSS rescore
  6. 2026-08-12 09:55 UTCGHSA enrichment
  7. 2026-08-11 21:06 UTCEG score recompute
  8. 2026-08-11 21:06 UTCGHSA enrichment
  9. 2026-08-11 13:42 UTCEPSS rescore
  10. 2026-08-11 08:17 UTCEG score recompute
  11. 2026-08-11 08:17 UTCGHSA enrichment
  12. 2026-08-10 23:59 UTCEPSS rescore
  13. 2026-08-10 19:28 UTCEG score recompute
  14. 2026-08-10 19:28 UTCGHSA enrichment
  15. 2026-08-10 18:23 UTCGHSA enrichment
  16. 2026-08-10 05:34 UTCGHSA enrichment
  17. 2026-08-09 16:46 UTCEG score recompute
  18. 2026-08-09 16:46 UTCGHSA enrichment
  19. 2026-08-09 13:46 UTCEPSS rescore
  20. 2026-08-09 03:57 UTCEG score recompute
  21. 2026-08-09 03:57 UTCGHSA enrichment
  22. 2026-08-08 16:37 UTCEPSS rescore
  23. 2026-08-08 15:09 UTCGHSA enrichment
  24. 2026-08-08 02:20 UTCEG score recompute
  25. 2026-08-08 01:27 UTCEG score recompute
  26. 2026-08-08 01:27 UTCMITRE cvelistV5first tracked

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 in the National Vulnerability Database on August 8, 2026, with the most recent update on August 10, 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% probability of exploitation in the next 30 days, which ranks it in the top 83.0% of all scored CVEs.
What is the CVSS score of CVE-2026-13505?
CVE-2026-13505 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-13505?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13505, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs