CVE-2026-63574: Unbounded allocation from OpenPGP signature and user attribute subpacket lengths

Published Oct 2, 2026
·
Updated

Memory allocation with excessive size value in the OpenPGP signature and user attribute subpacket parsers (SignatureSubpacketsParser.ReadPacket, UserAttributeSubpacketsParser.ReadPacket) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows a remote, unauthenticated attacker who can supply a crafted OpenPGP public key, certificate or signature to cause a denial of service (OutOfMemoryException or memory exhaustion in the parsing process) via a subpacket header using the five-octet length form, because the declared length was used to size the subpacket buffer with no upper bound and without being compared with the size of the enclosing subpacket area or packet, so a few bytes of input could demand an allocation of up to about 2 GB before any subpacket data was read.

Affected Software

2 affected components
Legion of the Bouncy Castle Inc. bc-csharp<2.7.0
bouncycastle bc-csharp<2.7.0

Event History

Oct 2, 2026
CVE Published
via MITRE·07:06 AM
Data Sourced
via MITRE·07:06 AM
DescriptionWeakness
Data Sourced
via OSV·07:06 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:17 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:17 AM
RemedyAffected Software

Frequently Asked Questions

1

Which deployments are exposed to this denial-of-service issue?

Deployments using bc-csharp before version 2.7.0 are affected if they parse OpenPGP public keys, certificates, or signatures that can be supplied by a remote party. The vulnerable code paths are the signature and user attribute subpacket parsers.

2

What does an attacker need to exploit the issue?

An attacker does not need authentication or user interaction. They need only to provide a crafted OpenPGP public key, certificate, or signature containing a subpacket header encoded with the five-octet length form.

3

What is the operational impact of successful exploitation?

The parsing process can attempt to allocate up to about 2 GB based on only a few bytes of attacker-controlled input. This can trigger an OutOfMemoryException or exhaust available memory, causing denial of service.

4

Is immediate mitigation available if upgrading is delayed?

The provided information identifies version 2.7.0 as the fixed boundary but does not specify a workaround. Until an upgrade is possible, reduce or prevent parsing of untrusted OpenPGP keys, certificates, and signatures where feasible.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203