CVE-2026-15997

LOWPre-NVD 1.71.7
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 1.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 97% 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
1.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 1.7Exploit: None knownExposed: 0

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

Out-of-bounds write vulnerability in Legion of the Bouncy Castle Inc. BC-LTS bcprov-lts8on on ARM allows Overflow Buffers.

This vulnerability is associated with program files https://github.Com/bcgit/bc-lts-java/blob/main/native_c/arm/sha/shake.C, https://github.Com/bcgit/bc-lts-java/blob/main/native_c/arm/sha/sha3.C.

This issue affects BC-LTS: from 2.73.0 before 2.73.12.1.

Issue is only applicable if application involved is accepting memoable SHA3 / SHAKE states from potentially untrusted sources.

CVSS v3
1.7
EG Score
1.7(medium)
EG Risk
8(Track)
EG Risk 8/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
Severity17% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 16, 2026

Last Modified

July 17, 2026

References (1)

Vendor Advisories for CVE-2026-15997(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 9× in last 7d / 42× 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-30 03:28 UTCEG score recompute
  2. 2026-08-30 03:28 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 14:46 UTCEPSS rescore
  7. 2026-08-25 13:48 UTCEPSS rescore
  8. 2026-08-25 12:59 UTCEG score recompute
  9. 2026-08-25 12:59 UTCGHSA enrichment
  10. 2026-08-23 00:19 UTCEPSS rescore
  11. 2026-08-22 12:48 UTCEG score recompute
  12. 2026-08-22 12:48 UTCGHSA enrichment
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-19 17:03 UTCEPSS rescore
  16. 2026-08-19 12:50 UTCEG score recompute
  17. 2026-08-19 12:50 UTCGHSA enrichment
  18. 2026-08-17 13:47 UTCEPSS rescore
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 12:50 UTCEG score recompute
  21. 2026-08-16 12:50 UTCGHSA enrichment
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-13 12:52 UTCEG score recompute
  25. 2026-08-13 12:52 UTCGHSA enrichment
Show 38 more
  1. 2026-08-12 13:50 UTCEPSS rescore
  2. 2026-08-11 00:00 UTCEPSS rescore
  3. 2026-08-10 12:54 UTCEG score recompute
  4. 2026-08-10 12:54 UTCGHSA enrichment
  5. 2026-08-08 16:37 UTCEPSS rescore
  6. 2026-08-07 12:57 UTCEG score recompute
  7. 2026-08-07 12:57 UTCGHSA enrichment
  8. 2026-08-06 13:46 UTCEPSS rescore
  9. 2026-08-05 19:17 UTCEPSS rescore
  10. 2026-08-04 15:10 UTCEPSS rescore
  11. 2026-08-04 13:00 UTCEG score recompute
  12. 2026-08-04 13:00 UTCGHSA enrichment
  13. 2026-08-04 10:38 UTCEPSS rescore
  14. 2026-08-03 10:35 UTCEPSS rescore
  15. 2026-08-01 11:18 UTCEG score recompute
  16. 2026-08-01 11:18 UTCGHSA enrichment
  17. 2026-08-01 04:15 UTCEPSS rescore
  18. 2026-07-30 01:30 UTCEPSS rescore
  19. 2026-07-29 11:21 UTCEG score recompute
  20. 2026-07-29 11:21 UTCGHSA enrichment
  21. 2026-07-27 14:13 UTCEPSS rescore
  22. 2026-07-26 11:23 UTCEG score recompute
  23. 2026-07-26 11:23 UTCGHSA enrichment
  24. 2026-07-25 14:17 UTCEPSS rescore
  25. 2026-07-24 14:17 UTCEPSS rescore
  26. 2026-07-23 14:18 UTCEPSS rescore
  27. 2026-07-23 03:05 UTCEG score recompute
  28. 2026-07-22 14:08 UTCEPSS rescore
  29. 2026-07-21 15:24 UTCEPSS rescore
  30. 2026-07-20 17:08 UTCEPSS rescore
  31. 2026-07-19 14:30 UTCEPSS rescore
  32. 2026-07-19 02:32 UTCEG score recompute
  33. 2026-07-19 02:32 UTCGHSA enrichment
  34. 2026-07-18 10:04 UTCEPSS rescore
  35. 2026-07-17 13:36 UTCEG score recompute
  36. 2026-07-17 13:36 UTCGHSA enrichment
  37. 2026-07-16 23:43 UTCEG score recompute
  38. 2026-07-16 23:43 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-15997?
CVE-2026-15997 is a low vulnerability published on July 16, 2026. Out-of-bounds write vulnerability in Legion of the Bouncy Castle Inc. BC-LTS bcprov-lts8on on ARM allows Overflow Buffers. This vulnerability is associated with program files https://github.Com/bcgit/bc-lts-java/blob/main/nativec/arm/sha/shake.C,…
When was CVE-2026-15997 disclosed?
CVE-2026-15997 was first published in the National Vulnerability Database on July 16, 2026, with the most recent update on July 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15997 actively exploited?
CVE-2026-15997 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 96.7% of all scored CVEs.
What is the CVSS score of CVE-2026-15997?
CVE-2026-15997 has a CVSS v3 base score of 1.7 (NVD).
How do I remediate CVE-2026-15997?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15997, 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-15997

Explore →

Is Your Infrastructure Affected by CVE-2026-15997?

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