CVE-2026-5588

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.6%, top 51% 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.

Use of a Broken or Risky Cryptographic Algorithm vulnerability in Legion of the Bouncy Castle Inc. BC-JAVA bcpkix on all (pkix modules), Legion of the Bouncy Castle Inc. BCPKIX-FIPS bcpkix on All (pkix modules), Legion of the Bouncy Castle Inc. BCPIX-LTS bcpkix on All (pkix modules).

This vulnerability is associated with program files JcaContentVerifierProviderBuilder.Java, JcaContentVerfierProviderBuilder.Java.

This issue affects BC-JAVA: from 1.67 before 1.80.2, from 1.81 before 1.81.1, from 1.82 before 1.84; BCPKIX-FIPS: from 2.0.6 before 2.0.11, from 2.1.7 before 2.1.11; BCPIX-LTS: from 2.73.7 before 2.73.11.

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
49%
KEV
Not listed

Published

April 15, 2026

Last Modified

September 18, 2026

Advisory Details (2)

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

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

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

ensured generic composite always checks at least one signature. Added… · bcgit/bc-java@656bae0 · GitHub

https://github.com/bcgit/bc-java/commit/656bae0dbd9b1521f840521ff786e78749fe3057

Patch Availability(19)

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

(11 across 5 ecosystems)
Maven(7)
PackageVulnerable rangeFixed inDependents
org.bouncycastle:bcpkix-debug-jdk141.81, 1.82, 1.831.84
org.bouncycastle:bcpkix-debug-jdk15to181.73 ... 1.83 (12 versions)1.84
org.bouncycastle:bcpkix-debug-jdk18on1.73 ... 1.83 (11 versions)1.84
org.bouncycastle:bcpkix-jdk141.49 ... 1.83 (34 versions)1.84
org.bouncycastle:bcpkix-jdk15on1.49 ... 1.70 (22 versions)1.84
org.bouncycastle:bcpkix-jdk15to181.63 ... 1.83 (22 versions)1.84
org.bouncycastle:bcpkix-jdk18on1.71 ... 1.83 (15 versions)1.84
Debian:11(1)
PackageVulnerable rangeFixed inDependents
bouncycastle1.68-2 ... 1.80-3 (12 versions)
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(2)

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

Additional Vendor Advisories

(6)

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-5588?
CVE-2026-5588 is a high vulnerability published on April 15, 2026. Use of a Broken or Risky Cryptographic Algorithm vulnerability in Legion of the Bouncy Castle Inc. BC-JAVA bcpkix on all (pkix modules), Legion of the Bouncy Castle Inc. BCPKIX-FIPS bcpkix on All (pkix modules), Legion of the Bouncy Castle Inc. BCPIX-LTS bcpkix on All (pkix modules). This…
When was CVE-2026-5588 disclosed?
CVE-2026-5588 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-5588 actively exploited?
CVE-2026-5588 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 50.8% of all scored CVEs.
What is the CVSS score of CVE-2026-5588?
CVE-2026-5588 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-5588?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5588, 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-5588

Explore →

Is Your Infrastructure Affected by CVE-2026-5588?

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