Is org.bouncycastle:bcprov-jdk18on 1.84 vulnerable?

Maven · 1 release from 1.84.0 to 1.84.0 · latest org.bouncycastle:bcprov-jdk18on is 1.87 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. org.bouncycastle:bcprov-jdk18on 1.84.0, the last 1.84 release, is affected by 2 known security advisories (1 critical, 1 high), including CVE-2026-8763, CVE-2026-13506. Upgrade to 1.85 or later to fix all of them.

Upgrade with:mvn versions:use-dep-version -Dincludes=org.bouncycastle:bcprov-jdk18on -DdepVersion=1.85 -DforceVersion=true

Is your project on an affected org.bouncycastle:bcprov-jdk18on?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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.84.0

  • HighCVE-2026-13506GHSA-qp49-qgx5-5m263 Aug 2026

    Bouncy Castle: Lazy ASN.1 sequence forcing resets nesting-depth guard

    Affected
    <1.85
    Fixed in
    1.85
  • CriticalCVE-2026-8763GHSA-9pwp-9qqc-pr263 Aug 2026

    Bouncy Castle: Name Constraints bypass via trailing dot in rfc822Name and URI

    Affected
    <1.85
    Fixed in
    1.85

Which of your client projects are still on org.bouncycastle:bcprov-jdk18on 1.84?

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.