What is CVE-2007-6721?

CVE-2007-6721 is a high-severity security vulnerability in bouncycastle:bcprov-jdk14 (maven), affecting versions < 1.38. It is fixed in 1.38.

Which packages are affected by CVE-2007-6721?

bouncycastle:bcprov-jdk14 (maven) versions < 1.38; bouncycastle:bcprov-jdk15 (maven) versions < 1.38; bouncycastle:bcprov-jdk16 (maven) versions < 1.38.

Is there a fix for CVE-2007-6721?

Yes. CVE-2007-6721 is fixed in 1.38. Upgrade to this version or later.

Is CVE-2007-6721 exploitable, and should I be worried?

Whether CVE-2007-6721 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2007-6721 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2007-6721 in bouncycastle:bcprov-jdk14

Q: Which packages are affected by CVE-2007-6721?

bouncycastle:bcprov-jdk14 (maven) versions < 1.38; bouncycastle:bcprov-jdk15 (maven) versions < 1.38; bouncycastle:bcprov-jdk16 (maven) versions < 1.38.

Q: Is there a fix for CVE-2007-6721?

Yes. CVE-2007-6721 is fixed in 1.38. Upgrade to this version or later.

Q: Is CVE-2007-6721 exploitable, and should I be worried?

Whether CVE-2007-6721 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2007-6721 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2007-6721?

Upgrade: bouncycastle:bcprov-jdk14 to 1.38 or later, bouncycastle:bcprov-jdk15 to 1.38 or later, bouncycastle:bcprov-jdk16 to 1.38 or later.

Summary

Legion of the Bouncy Castle Java Cryptography API Bleichenbacher Oracle Vulnerability

The Legion of the Bouncy Castle Java Cryptography API before release 1.38, as used in Crypto Provider Package before 1.36, has unknown impact and remote attack vectors related to "a Bleichenbacher vulnerability in simple RSA CMS signatures without signed attributes."

Impact

Affected versions

bouncycastle:bcprov-jdk14 (< 1.38) bouncycastle:bcprov-jdk15 (< 1.38) bouncycastle:bcprov-jdk16 (< 1.38)

Security releases

bouncycastle:bcprov-jdk14 → 1.38 (maven) bouncycastle:bcprov-jdk15 → 1.38 (maven) bouncycastle:bcprov-jdk16 → 1.38 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

bouncycastle:bcprov-jdk14 to 1.38 or later; bouncycastle:bcprov-jdk15 to 1.38 or later; bouncycastle:bcprov-jdk16 to 1.38 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2007-6721? CVE-2007-6721 is a high-severity security vulnerability in bouncycastle:bcprov-jdk14 (maven), affecting versions < 1.38. It is fixed in 1.38.
Which packages are affected by CVE-2007-6721?
- bouncycastle:bcprov-jdk14 (maven) (versions < 1.38)
- bouncycastle:bcprov-jdk15 (maven) (versions < 1.38)
- bouncycastle:bcprov-jdk16 (maven) (versions < 1.38)
Is there a fix for CVE-2007-6721? Yes. CVE-2007-6721 is fixed in 1.38. Upgrade to this version or later.
Is CVE-2007-6721 exploitable, and should I be worried? Whether CVE-2007-6721 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2007-6721 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2007-6721?
- Upgrade bouncycastle:bcprov-jdk14 to 1.38 or later
- Upgrade bouncycastle:bcprov-jdk15 to 1.38 or later
- Upgrade bouncycastle:bcprov-jdk16 to 1.38 or later