CVE-2025-14813

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.3%, top 76% 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: 0%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 bcprov on all (core modules).

This vulnerability is associated with program files G3413CTRBlockCipher.

This issue affects BC-JAVA: from 1.59 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
34(Track)
EG Risk 34/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%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

April 15, 2026

Last Modified

July 16, 2026

Advisory Details (3)

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

CVE‐2025‐14813 · bcgit/bc-java Wiki · GitHub

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

refactored counter code. · bcgit/bc-java@b425743 · GitHub

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

fixed one off error in G3413CTRBlockCipher · bcgit/bc-java@701686c · GitHub

https://github.com/bcgit/bc-java/commit/701686cb0184cd9ae103c801b3581fdf95c6d4f3

Vendor Advisories for CVE-2025-14813(12)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-modelmesh-rhel9:17800695062026-06-10redhat
redhatdevspaces/pluginregistry-rhel9:17793594232026-05-28redhat
redhateap8-bouncycastle-0:1.84.0-1.redhat_00001.1.el8eap2026-05-18redhat
redhateap8-bouncycastle-0:1.84.0-1.redhat_00001.1.el9eap2026-05-18redhat
redhatbcprov-jdk18on2026-05-18redhat
redhatbcprov-lts8on2026-05-14redhat

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

(12 across 1 ecosystem)
Maven(12)
PackageVulnerable rangeFixed inDependents
org.bouncycastle:bcprov-debug-jdk141.82, 1.831.84—
org.bouncycastle:bcprov-debug-jdk15to181.82, 1.831.84—
org.bouncycastle:bcprov-debug-jdk18on1.82, 1.831.84—
org.bouncycastle:bcprov-ext-debug-jdk141.60 ... 1.74 (8 versions)——
org.bouncycastle:bcprov-ext-debug-jdk15to181.68 ... 1.77 (10 versions)——
org.bouncycastle:bcprov-ext-debug-jdk18on1.71 ... 1.77 (7 versions)——
org.bouncycastle:bcprov-ext-jdk141.60 ... 1.78.1 (14 versions)——
org.bouncycastle:bcprov-ext-jdk15to181.64 ... 1.78.1 (14 versions)——
org.bouncycastle:bcprov-ext-jdk18on1.71 ... 1.78.1 (9 versions)——
org.bouncycastle:bcprov-jdk141.82, 1.831.84—
org.bouncycastle:bcprov-jdk15to181.82, 1.831.84—
org.bouncycastle:bcprov-jdk18on1.82, 1.831.84—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 41× 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 164 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-14813?
CVE-2025-14813 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 bcprov on all (core modules). This vulnerability is associated with program files G3413CTRBlockCipher. This issue affects BC-JAVA: from 1.59 before 1.80.2, from 1.81 before 1.81.1, from 1.82…
When was CVE-2025-14813 disclosed?
CVE-2025-14813 was first published in the National Vulnerability Database on April 15, 2026, with the most recent update on July 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-14813 actively exploited?
CVE-2025-14813 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 76.4% of all scored CVEs.
What is the CVSS score of CVE-2025-14813?
CVE-2025-14813 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2025-14813?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-14813, 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-2025-14813

Explore →

Is Your Infrastructure Affected by CVE-2025-14813?

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

Start Free Scan →Browse All CVEs