CriticalGHSA-9pwp-9qqc-pr26CVE-2026-8763

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

Published 3 Aug 2026 · Updated 18 Sept 2026

Is your project on an affected org.bouncycastle:bc-fips?

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

Affected packages

Affected
<1.0.2.7
Fixed in
1.0.2.7
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.bouncycastle:bc-fips -DdepVersion=1.0.2.7 -DforceVersion=true
Affected
>=2.0.0 <2.0.2
Fixed in
2.0.2
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.bouncycastle:bc-fips -DdepVersion=2.0.2 -DforceVersion=true
Affected
>=2.1.0 <2.1.3
Fixed in
2.1.3
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.bouncycastle:bc-fips -DdepVersion=2.1.3 -DforceVersion=true
Affected
<1.85
Fixed in
1.85
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.bouncycastle:bcprov-jdk18on -DdepVersion=1.85 -DforceVersion=true
Affected
<2.73.12
Fixed in
2.73.12
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.bouncycastle:bcprov-lts8on -DdepVersion=2.73.12 -DforceVersion=true
Affected
<1.85
Fixed in
1.85
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.bouncycastle:bcprov-jdk15to18 -DdepVersion=1.85 -DforceVersion=true

Details

In Bouncy Castle for Java before 1.85, Name Constraints bypass via trailing dot in rfc822Name and URI. This issue also affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before bc-fips 1.0.2.7 (1.0.X series), 2.0.2 (2.0.X series) and 2.1.3 (2.1.X series).

Is GHSA-9pwp-9qqc-pr26 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.bouncycastle:bc-fips, and gives you the command that fixes it.

More advisories for org.bouncycastle:bc-fips

  • HighCVE-2026-13505Bouncy Castle: Zeroisation of sensitive key material on garbage collection relies on finalization. · 8 Aug 2026
  • HighCVE-2026-8798Bouncy Castle: the native entropy source used on Intel platforms retried the CPU entropy instructions without any bound · 8 Aug 2026
  • HighCVE-2026-13506Bouncy Castle: Lazy ASN.1 sequence forcing resets nesting-depth guard · 3 Aug 2026
  • MediumCVE-2025-12194Bouncy Castle Vulnerable to Uncontrolled Resource Consumption · 25 Oct 2025
  • LowCVE-2025-9340Bouncy Castle for Java has Out-of-Bounds Write Vulnerability · 22 Aug 2025
  • MediumCVE-2025-9341Bouncy Castle for Java has Uncontrolled Resource Consumption Vulnerability · 22 Aug 2025
All 13 advisories for org.bouncycastle:bc-fips

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.