Skip to main content
VulnerabilityPublished Updated

CVE-2026-63573: Observable Discrepancy

Source GCVE Database

0
Authoritative record:CVE-2026-63573· High 8.2

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

Data as of 28 Oct 2026, 17:11 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% 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:H/VI:N/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. Weaponised: 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 26 Oct 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

A fixed version 2.7.0 or later of Legion of the Bouncy Castle Inc. bc-csharp addresses this issue. Until then, avoid processing untrusted CMS EnvelopedData messages with vulnerable versions.

Description

A vulnerability in Legion of the Bouncy Castle Inc. bc-csharp before version 2.7.0 allows an attacker to recover the content-encryption key from a captured CMS EnvelopedData message. This is due to an observable difference in error messages during RSA PKCS#1 v1.5 key-transport unwrap, enabling a Bleichenbacher-style adaptive chosen-ciphertext attack.

References

Community reviews

Loading reviews…