CVE-2026-14682
Bouncy Castle Java can be forced to allocate unbounded memory leading to OOM/DoS.
Is CVE-2026-14682 being exploited?
Not confirmed. CVE-2026-14682 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.31% probability of exploitation in the next 30 days.
How severe is CVE-2026-14682?
CVE-2026-14682 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-14682?
Yes. A fix has been recorded for CVE-2026-14682. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-14682 affect?
CVE-2026-14682 affects Bouncy Castle for Java < 1.85, Bouncy Castle for Java LTS < 2.73.12, BC-FIPS bc-fips < 1.0.2.7 / 2.0.2 / 2.1.3, bctls-fips < 1.0.24. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-14682?
Upgrade to BC Java 1.85 or LTS 2.73.12 and update bc-fips/bctls-fips to fixed releases.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted input triggers unbounded allocation on definite-length read, causing out-of-memory and service crash (Denial of Service).
Patch when possible
- affected>= 1.0.0 and < 1.0.2.7
- affected>= 2.0.0 and < 2.0.2
- affected>= 2.1.0 and < 2.1.3
- affected>= 1.0.0 and < 1.0.24
- affected< 1.85
- affected>= 2.73.0 and < 2.73.12
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.