How severe is CVE-2024-14041?

CVE-2024-14041 has a CVSS 3.x base score of 5.9, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2024-14041 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (26th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2024-14041?

CVE-2024-14041 affects Bouncycastle Bc-java. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2024-14041?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2024-14041 published?

CVE-2024-14041 was published on 2026-07-28 and last updated on 2026-10-02.

CVE-2024-14041

CVE-2024-14041 is a medium-severity vulnerability in Bouncycastle Bc-java with a CVSS 3.x base score of 5.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-208.

Key facts

Severity: Medium (CVSS 3.x base score 5.9)
CVSS v4: 8.2
EPSS exploit prediction: 0% (26th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-208
Affected product: Bouncycastle Bc-java
Published: 2026-07-28
Last modified: 2026-10-02

Description

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. These are the KyberSlash1 (Poly.toMsg) and KyberSlash2 (ciphertext compression) divisions. Compression performed during encapsulation operates on values that become the public ciphertext and is not affected.

Frequently asked questions

What is CVE-2024-14041?: 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. These are the KyberSlash1 (Poly.toMsg) and KyberSlash2 (ciphertext compression) divisions. Compression performed during encapsulation operates on values that become the public ciphertext and is not affected.
How severe is CVE-2024-14041?: CVE-2024-14041 has a CVSS 3.x base score of 5.9, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2024-14041 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (26th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-14041?: CVE-2024-14041 affects Bouncycastle Bc-java. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-14041?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2024-14041 published?: CVE-2024-14041 was published on 2026-07-28 and last updated on 2026-10-02.

References

Affected products (1)

cpe:2.3:a:bouncycastle:bc-java:*:*:*:*:*:*:*:*

More vulnerabilities in Bouncycastle Bc-java

CVE-2007-6721 — Critical (CVSS 10.0): The Legion of the Bouncy Castle Java Cryptography API before release 1.38, as used in Crypto Provider Package before…
CVE-2018-1000613 — Critical (CVSS 9.8): Legion of the Bouncy Castle Legion of the Bouncy Castle Java Cryptography APIs 1.58 up to but not including 1.60…
CVE-2026-58062 — Critical (CVSS 9.1): In Bouncy Castle for Java before 1.85, Stapled OCSP response accepted without binding to the checked certificate. This…
CVE-2026-8763 — Critical (CVSS 9.1): In Bouncy Castle for Java before 1.85, Name Constraints bypass via trailing dot in rfc822Name and URI. This issue also…
CVE-2026-59650 — Critical (CVSS 9.1): In Bouncy Castle for Java before 1.85, MTI/A0 DH agreement exponentiates unvalidated peer value. This issue also…
CVE-2026-12817 — High (CVSS 8.6): In Bouncy Castle for Java before 1.85, OpenPGP AEAD decryption skips final tag on chunk-aligned data. This issue also…

All CVEs affecting Bouncycastle Bc-java →

Other CWE-208 vulnerabilities

CVE-2026-77987 — Critical (CVSS 9.8): A server-side request forgery (SSRF) vulnerability was identified in the notebook viewer of GitHub Enterprise Server.…
CVE-2023-41313 — Critical (CVSS 9.8): The authentication method in Apache Doris versions before 2.0.0 was vulnerable to timing attacks. Users are recommended…
CVE-2026-63132 — Critical (CVSS 9.2): OpenBao is an open source identity-based secrets management system. Prior to 2.6.0, OpenBao's handleLogicalRecovery…
CVE-2026-16315 — High (CVSS 8.7): OMICRON StationGuard before version 4.10 contains a cryptographic timing side-channel vulnerability in the backend…
CVE-2024-42512 — High (CVSS 8.6): Vulnerability in the OPC UA .NET Standard Stack before 1.5.374.158 allows an unauthorized attacker to bypass…
CVE-2026-43606 — High (CVSS 8.5): Observable Timing Discrepancy in the AMD Vitis Libraries ECDSA secp256k1 component could allow attackers with local…

Browse all CWE-208 vulnerabilities →