CVE-2024-14041
Timing side-channel in Bouncy Castle Kyber routines allows private key recovery.
Is CVE-2024-14041 being exploited?
Not confirmed. CVE-2024-14041 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.34% probability of exploitation in the next 30 days.
How severe is CVE-2024-14041?
CVE-2024-14041 is rated High with a CVSS score of 8.2. 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-2024-14041?
Yes. A fix has been recorded for CVE-2024-14041. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-14041 affect?
CVE-2024-14041 affects Bouncy Castle for Java 1.73 - <1.78, Java apps using CRYSTALS-Kyber KEM via Bouncy Castle. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2024-14041?
Upgrade to Bouncy Castle >=1.78 and rotate Kyber keys; mitigate timing exposure.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker measuring many Kyber decapsulation timings can recover long-term private keys (secret key recovery).
Immediate action required
- affected>= 1.73 and < 1.78
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.