Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15
CVE-2015-7940GHSA-4mv7-cq75-3qjm
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.bouncycastle:bcprov-jdk14 1.51; org.bouncycastle:bcprov-jdk15 1.51; org.bouncycastle:bcprov-jdk15on 1.51), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven org.bouncycastle:bcprov-jdk14
- Affected
- < 1.51
- Fixed in
- 1.51
Maven org.bouncycastle:bcprov-jdk15
- Affected
- < 1.51
- Fixed in
- 1.51
Maven org.bouncycastle:bcprov-jdk15on
- Affected
- < 1.51
- Fixed in
- 1.51
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-4mv7-cq75-3qjm lists affected ranges: Maven org.bouncycastle:bcprov-jdk15 >=0 =0 =0 <1.51
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- CVE-2015-7940: 4.69% estimated exploitation activity in the next 30 days; percentile 91.80 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
The Bouncy Castle Java library before 1.51 does not validate a point is withing the elliptic curve, which makes it easier for remote attackers to obtain private keys via a series of crafted elliptic curve Diffie Hellman (ECDH) key exchanges, aka an "invalid curve attack."
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-4mv7-cq75-3qjm
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2015-7940 Advisory: Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15 IDs: CVE-2015-7940, GHSA-4mv7-cq75-3qjm Record: https://patchnext.com/advisories/cve-2015-7940 (revision 1, source checked 26 Oct 2026, 16:40 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: org.bouncycastle:bcprov-jdk14 1.51; org.bouncycastle:bcprov-jdk15 1.51; org.bouncycastle:bcprov-jdk15on 1.51. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.bouncycastle:bcprov-jdk14: affected < 1.51; fixed in 1.51 - Maven org.bouncycastle:bcprov-jdk15: affected < 1.51; fixed in 1.51 - Maven org.bouncycastle:bcprov-jdk15on: affected < 1.51; fixed in 1.51 ## Suggested inspection (read-only) - Maven org.bouncycastle:bcprov-jdk14: check the installed version with your package manager. - Maven org.bouncycastle:bcprov-jdk15: check the installed version with your package manager. - Maven org.bouncycastle:bcprov-jdk15on: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on org.bouncycastle:bcprov-jdk14, org.bouncycastle:bcprov-jdk15, org.bouncycastle:bcprov-jdk15on. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-4mv7-cq75-3qjm (GitHub-reviewed advisory GHSA-4mv7-cq75-3qjm lists affected ranges: Maven org.bouncycastle:bcprov-jdk15 >=0 =0 =0 <1.51) Commands are suggestions: review each one before running it.
Loading voting…