CVE-2026-103603

Unbounded HSS public key level count allows huge array allocation during signature verification

  • High 8.7

Description

Memory allocation with excessive size value in the HSS/LMS signature code (HssPublicKeyParameters, HssSignature) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows a remote unauthenticated attacker who can supply both an HSS public key and a signature to cause a denial of service through memory exhaustion via a public key encoding with an excessive level count, because the level count L read when parsing an HSS public key was not checked against the RFC 8554 maximum of 8, and signature parsing then allocated an array of L - 1 entries before reading any further signature data. A single verification can commit up to about 17 GB of memory or fail with an OutOfMemoryException.

Key facts

Published
2 Oct 2026
Last changed
2 Oct 2026
Assigned by
bcorg
EPSS
0.522% likely to be exploited in the next 30 days, higher than 44.932% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: yes; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 8.7CVSS 4.0, Highfrom the CNA (bcorg)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

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

Denial of Service (memory exhaustion during HSS signature verification) (CNA impact statement)

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Legion of the Bouncy Castle Inc.bc-csharp
  • Default status: unaffected
  • 0 up to but excluding 2.7.0 (affected)

Timeline

  1. 2 Oct 2026 Published

Weakness

References