Skip to content
Noroxi
CVE-2026-8763· NVD / CVE Program· CNA bcorg

Name Constraints bypass via trailing dot in rfc822Name and URI

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

CriticalCVSS 9.3 · v4.0—No exploit Fix available
Published
Aug 2, 2026
Updated
Sep 2, 2026
EPSS
0.4% · 35th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

37

Monitor

Low priority for now.

CVSS
37 / 40 · 9.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · bcorg
9.3
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/U:Amber

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
bouncycastlebc-java
bouncycastlebouncy castle for java lts
bouncycastlefips java api

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • bouncycastle bc-javabefore 1.85
  • bouncycastle bouncy castle for java ltsup to 2.73.11 inclusive
  • bouncycastle fips java api1.0.0 and later · before 1.0.2.7
  • bouncycastle fips java api2.0.0 and later · before 2.0.2
  • bouncycastle fips java api2.1.0 and later · before 2.1.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (bcorg). Independent of NVD's CPE analysis and usually ahead of it.

  • Legion of the Bouncy Castle Inc. BC-FJA

    • 1.0.0 and later · before 1.0.2.7affected · maven
    • 2.0.0 and later · before 2.0.2affected · maven
    • 2.1.0 and later · before 2.1.3affected · maven
  • Legion of the Bouncy Castle Inc. BC-JAVA

    • before 1.85affected · maven
  • Legion of the Bouncy Castle Inc. BC-LTS-JAVA

    • 2.73.0 and later · before 2.73.12affected · maven

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12bouncycastleall versions—
Mavenorg.bouncycastle:bc-fipsfrom 2.0.0 · before 2.0.22.0.2
Mavenorg.bouncycastle:bc-fipsfrom 2.1.0 · before 2.1.32.1.3
Mavenorg.bouncycastle:bc-fipsbefore 1.0.2.71.0.2.7
Mavenorg.bouncycastle:bcprov-jdk15to18before 1.851.85
Mavenorg.bouncycastle:bcprov-jdk18onbefore 1.851.85
Mavenorg.bouncycastle:bcprov-lts8onbefore 2.73.122.73.12

Other highest-scoring records for the same primary product.

  • CVE-2007-6721The Legion of the Bouncy Castle Java Cryptography API before release 1.38, as used in Crypto Provider Package before 1.36, has unknown impac
    41Plan
  • CVE-2018-1000613Legion of the Bouncy Castle Legion of the Bouncy Castle Java Cryptography APIs 1.58 up to but not including 1.60 contains a CWE-470: Use of
    40Plan
  • CVE-2026-58062Stapled OCSP response accepted without binding to the checked certificate
    37Monitor
  • CVE-2026-59650MTI/A0 DH agreement exponentiates unvalidated peer value
    37Monitor
  • CVE-2026-59638JSSE hostname verifier CN-fallback enabled by default despite documented opt-in
    37Monitor
  • CVE-2026-14682Possible OOM from unbounded up-front allocation on a definite-length read
    34Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Legion of the Bouncy Castle Inc. BC-FJA1.0.2.7Vendor (CNA)
Legion of the Bouncy Castle Inc. BC-FJA2.0.2Vendor (CNA)
Legion of the Bouncy Castle Inc. BC-FJA2.1.3Vendor (CNA)
Legion of the Bouncy Castle Inc. BC-JAVA1.85Vendor (CNA)
Legion of the Bouncy Castle Inc. BC-LTS-JAVA2.73.12Vendor (CNA)
Maven:org.bouncycastle:bc-fips1.0.2.7Package registry (OSV)
Maven:org.bouncycastle:bc-fips2.0.2Package registry (OSV)
Maven:org.bouncycastle:bc-fips2.1.3Package registry (OSV)
Maven:org.bouncycastle:bcprov-jdk15to181.85Package registry (OSV)
Maven:org.bouncycastle:bcprov-jdk18on1.85Package registry (OSV)
Maven:org.bouncycastle:bcprov-lts8on2.73.12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-580620 days apartStapled OCSP response accepted without binding to the checked certificate
    37Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
X

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:Amber

nvd-secondary

Root cause

A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

kotlin
override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) {  // Left empty for the test environment}

Fixed

kotlin
val client = OkHttpClient.Builder()  .certificatePinner(    CertificatePinner.Builder()      .add("api.sirius.example", "sha256/…")      .build()  ).build()

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records