CVE-2026-12817
Bouncy Castle OpenPGP AEAD decryption skips final tag on chunk-aligned data.
Is CVE-2026-12817 being exploited?
Not confirmed. CVE-2026-12817 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.14% probability of exploitation in the next 30 days.
How severe is CVE-2026-12817?
CVE-2026-12817 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-12817?
Yes. A fix has been recorded for CVE-2026-12817. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-12817 affect?
CVE-2026-12817 affects Bouncy Castle for Java < 1.85, Bouncy Castle for Java LTS < 2.73.12, BC-FJA (bcpg-fips) < 1.0.13 (1.0.X), BC-FJA < 2.0.13 (2.0.X), and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-12817?
Upgrade to Bouncy Castle 1.85 / LTS 2.73.12 / respective BC-FJA fixed versions immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Integrity bypass: crafted OpenPGP AEAD ciphertext may be accepted without final-tag check, enabling tampering or potential plaintext recovery during decryption.
Patch when possible
- affected>= 1.0.7 and < 1.0.13
- affected>= 2.0.0 and < 2.0.13
- affected>= 2.1.0 and < 2.1.13
- affected>= 1.74 and < 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.