Advisory severityMedium5.9Red Hat Linux

Medium [CVE-2024-14041] Bouncy Castle for Java: Private key recovery via timing side-channel in ML-KEM (CRYSTALS-Kyber) routines

This medium-severity Red Hat Linux advisory covers CVE-2024-14041 affecting Red Hat JBoss Enterprise Application Platform Expansion Pack.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2024-14041 Source published Jul 28, 2026Source updated Jul 28, 2026

VulniPulse record published Aug 14, 2026Record updated Aug 14, 2026

CVE-2024-14041

Affected products & platforms

Red Hat LinuxUnclassified

Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Get CVE alerts See app features

Summary

In Bouncy Castle for Java from 1.73 to before 1.78, three ML-KEM (CRYSTALS-Kyber) routines divided secret-derived polynomial coefficients by the modulus q: Poly.toMsg, which decodes the decrypted message, and the ciphertext compression routines Poly.compressPoly and PolyVec.compressPolyVec.

An attacker able to measure the timing of a large number of decapsulations performed with the same long-term private key can recover that key. Compression performed during encapsulation operates on values that become the public ciphertext and is not affected.

Successful exploitation allows the attacker to recover the long-term private key, leading to a significant compromise of cryptographic security. Red Hat severity: Moderate — CVSS 5.9 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N).

Weakness: CWE-208. Affected Red Hat products: Red Hat JBoss Enterprise Application Platform Expansion Pack.

Red Hat does not currently list a fixing RHSA for this CVE.

Affected versions

< 1.73
< 1.78

Official advisory · high-confidence parse· fetched 2 days ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 2 days ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · high-confidence parse· fetched 2 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.