CVE-2026-5598

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9%, top 42% 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Covert timing channel vulnerability in Legion of the Bouncy Castle Inc. BC-JAVA core on all (core modules).

This vulnerability is associated with program files FrodoEngine.Java.

This issue affects BC-JAVA: from 1.71 before 1.80.2, from 1.81 before 1.81.1, from 1.82 before 1.84.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
58%
KEV
Not listed

Published

April 15, 2026

Last Modified

September 18, 2026

Advisory Details (3)

Auto-updated May 2, 2026
No patch confirmed yet.
generic

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

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

Fix Frodo error sampling to be constant-time · bcgit/bc-java@94abbd5 · GitHub

https://github.com/bcgit/bc-java/commit/94abbd56413dfdac651fd878bc60253871ef5e87
generic

Refactoring in pqc.crypto.frodo · bcgit/bc-java@8692e6b · GitHub

https://github.com/bcgit/bc-java/commit/8692e6b2b191fc4aafa32545c7a78bdb9bf110c5

Vendor Advisories for CVE-2026-5598(8)

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

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
redhateap7-wildfly-0:7.4.25-2.GA_redhat_00001.1.el7eap2026-08-11redhat
redhateap7-wildfly-0:7.4.25-2.GA_redhat_00001.1.el9eap2026-08-11redhat
redhateap7-wildfly-0:7.4.25-2.GA_redhat_00001.1.el8eap2026-08-11redhat
redhatbcprov-jdk122026-08-11redhat
redhateap8-bouncycastle-0:1.84.0-1.redhat_00001.1.el9eap2026-05-18redhat
redhatorg.bouncycastle/bcprov-jdk18on:1.84.0.redhat-000012026-05-18redhat
redhateap8-bouncycastle-0:1.84.0-1.redhat_00001.1.el8eap2026-05-18redhat
redhateap7-bouncycastle-0:1.84.0-1.redhat_00001.1.el9eap2026-04-30redhat
redhatpatch2026-04-30redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 4 ecosystems)
Maven(3)
PackageVulnerable rangeFixed inDependents
org.bouncycastle:bcprov-jdk141.811.81.1—
org.bouncycastle:bcprov-jdk15to181.71 ... 1.80 (11 versions)1.80.2—
org.bouncycastle:bcprov-jdk18on1.82, 1.831.84—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
bouncycastle1.72-2, 1.77-1, 1.80-1, 1.80-2, 1.80-3——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
bouncycastle1.80-3——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
bouncycastle1.80-3——

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 14× in last 7d / 37× 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 210 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-5598?
CVE-2026-5598 is a high vulnerability published on April 15, 2026. Covert timing channel vulnerability in Legion of the Bouncy Castle Inc. BC-JAVA core on all (core modules). This vulnerability is associated with program files FrodoEngine.Java. This issue affects BC-JAVA: from 1.71 before 1.80.2, from 1.81 before 1.81.1, from 1.82 before 1.84.
When was CVE-2026-5598 disclosed?
CVE-2026-5598 was first published in the National Vulnerability Database on April 15, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5598 actively exploited?
CVE-2026-5598 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 41.9% of all scored CVEs.
What is the CVSS score of CVE-2026-5598?
CVE-2026-5598 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-5598?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5598, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-5598?

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

Start Free Scan →Browse All CVEs