Skip to main content
CVE-2026-63574VulnerabilityPublished Updated

Excessive Memory Allocation

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-63574· High 8.7

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

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% 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:N/PR:N/UI:N/VC:N/VI:N/VA:H/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 16 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

A fixed version 2.7.0 or later of bc-csharp addresses this issue. Users should upgrade to version 2.7.0 or later to remediate this vulnerability. No other mitigation or workaround is indicated.

Description

A vulnerability in Legion of the Bouncy Castle Inc. bc-csharp before version 2.7.0 allows remote attackers to cause a denial of service via crafted OpenPGP subpackets. The flaw arises from memory allocation with an excessive size value in the OpenPGP signature and user attribute subpacket parsers, leading to potential memory exhaustion or OutOfMemoryException during parsing.

References

Community reviews

Loading reviews…