Skip to main content
CVE-2026-63577VulnerabilityPublished Updated

Improper Certificate Validation

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-63577· High 8.2

Not known to be exploited · CVSS 8.2 High : upgrade to 2.7.0 soon.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.7.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade bc-csharp and BouncyCastle.Cryptography to 2.7.0.

Affected software

ProductAffectedFixed in
Legion of the Bouncy Castle Inc.bc-csharpAffected
  • <2.7.0
Fixed in
  • 2.7.0
NuGetBouncyCastle.Cryptographypkg:nuget/BouncyCastle.CryptographyOther threatsAffected
  • <2.7.0
Fixed in
  • 2.7.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, users should consider avoiding use of affected versions or implement additional certificate validation checks externally to mitigate the risk.

Description

A vulnerability in the Legion of the Bouncy Castle Inc. bc-csharp library before version 2.7.0 allows improper certificate validation in the directoryName name-constraint check. This flaw permits an attacker controlling a name-constrained intermediate CA to have certificates accepted by PKIX path validation even when the subject name lies outside the CA's permitted subtrees. The issue arises because the validation incorrectly matches the constraint's first RDN anywhere in the name rather than requiring it as an initial prefix, violating RFC 5280 requirements.

References

Community reviews

Loading reviews…