Is org.bouncycastle:bcprov-jdk18on 1.83 vulnerable?
Maven · 1 release from 1.83.0 to 1.83.0 · latest org.bouncycastle:bcprov-jdk18on is 1.87 · checked 18 Nov 2026
Yes: 5 known advisories
Yes. org.bouncycastle:bcprov-jdk18on 1.83.0, the last 1.83 release, is affected by 5 known security advisories (2 critical, 2 high, 1 medium), including CVE-2026-8763, CVE-2025-14813, CVE-2026-13506. Upgrade to 1.85 or later to fix all of them.
mvn versions:use-dep-version -Dincludes=org.bouncycastle:bcprov-jdk18on -DdepVersion=1.85 -DforceVersion=trueIs your project on an affected org.bouncycastle:bcprov-jdk18on?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting org.bouncycastle:bcprov-jdk18on 1.83.0
Bouncy Castle: Lazy ASN.1 sequence forcing resets nesting-depth guard
- Affected
- <1.85
- Fixed in
- 1.85
Bouncy Castle: Name Constraints bypass via trailing dot in rfc822Name and URI
- Affected
- <1.85
- Fixed in
- 1.85
Bouncy Castle for Java GOST 28147 CTR mode reuses keystream after 255 blocks
- Affected
- >=1.59 <1.80.2 · >=1.81.0 <1.81.1 · >=1.82 <1.84
- Fixed in
- 1.80.2, 1.81.1, 1.84
Bouncy Castle Has Covert Timing Channel Vulnerability
- Affected
- >=1.82 <1.84 · >=1.81 <1.84 · >=1.71 <1.80.2
- Fixed in
- 1.80.2, 1.84
Bouncy Castle has an LDAP injection
- Affected
- >=1.74 <1.80.2 · >=1.81 <1.81.1 · >=1.82 <1.84
- Fixed in
- 1.80.2, 1.81.1, 1.84
Which of your client projects are still on org.bouncycastle:bcprov-jdk18on 1.83?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.bouncycastle:bcprov-jdk18on version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other org.bouncycastle:bcprov-jdk18on versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.