CVE-2026-63566: CWE-789 Memory Allocation with Excessive Size Value in Legion of the Bouncy Castle Inc. bc-csharp
Memory allocation with excessive size value in the DTLS handshake reassembly (DtlsReliableHandshake, DtlsReassembler) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows a remote unauthenticated DTLS peer to cause a denial of service through memory exhaustion via crafted handshake message fragments, because the reassembly buffer for each incoming handshake message was allocated at the 24-bit length declared in the fragment header, without the check against the peer's maximum handshake message size that TLS already applied. A fragment carrying no payload can force an allocation of almost 16 MB, for each of up to 16 pending messages per handshake, before the handshake is authenticated. DTLS servers and DTLS clients are both affected; TLS is not.
AI Analysis
Technical Summary
The vulnerability (CVE-2026-63566) exists in the DTLS handshake reassembly components (DtlsReliableHandshake, DtlsReassembler) of Legion of the Bouncy Castle Inc. bc-csharp versions prior to 2.7.0. The flaw allows a remote unauthenticated attacker to trigger excessive memory allocation by sending crafted handshake message fragments. The reassembly buffer is allocated according to the 24-bit length declared in the fragment header without verifying against the peer's maximum handshake message size, which TLS normally enforces. A fragment with no payload can cause allocation of nearly 16 MB per message, with up to 16 messages pending per handshake, leading to memory exhaustion and denial of service. Both DTLS clients and servers are vulnerable; TLS implementations are not affected.
Potential Impact
An unauthenticated remote attacker can cause denial of service by exhausting memory resources during the DTLS handshake process. This can disrupt availability of DTLS clients and servers using vulnerable versions of bc-csharp. There is no indication of confidentiality or integrity impact. The vulnerability does not affect TLS.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, consider limiting exposure of DTLS services to untrusted networks or applying network-level protections to mitigate crafted handshake fragments.
CVE-2026-63566: CWE-789 Memory Allocation with Excessive Size Value in Legion of the Bouncy Castle Inc. bc-csharp
Description
Memory allocation with excessive size value in the DTLS handshake reassembly (DtlsReliableHandshake, DtlsReassembler) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows a remote unauthenticated DTLS peer to cause a denial of service through memory exhaustion via crafted handshake message fragments, because the reassembly buffer for each incoming handshake message was allocated at the 24-bit length declared in the fragment header, without the check against the peer's maximum handshake message size that TLS already applied. A fragment carrying no payload can force an allocation of almost 16 MB, for each of up to 16 pending messages per handshake, before the handshake is authenticated. DTLS servers and DTLS clients are both affected; TLS is not.
CVSS v4.0
Score 8.7high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability (CVE-2026-63566) exists in the DTLS handshake reassembly components (DtlsReliableHandshake, DtlsReassembler) of Legion of the Bouncy Castle Inc. bc-csharp versions prior to 2.7.0. The flaw allows a remote unauthenticated attacker to trigger excessive memory allocation by sending crafted handshake message fragments. The reassembly buffer is allocated according to the 24-bit length declared in the fragment header without verifying against the peer's maximum handshake message size, which TLS normally enforces. A fragment with no payload can cause allocation of nearly 16 MB per message, with up to 16 messages pending per handshake, leading to memory exhaustion and denial of service. Both DTLS clients and servers are vulnerable; TLS implementations are not affected.
Potential Impact
An unauthenticated remote attacker can cause denial of service by exhausting memory resources during the DTLS handshake process. This can disrupt availability of DTLS clients and servers using vulnerable versions of bc-csharp. There is no indication of confidentiality or integrity impact. The vulnerability does not affect TLS.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, consider limiting exposure of DTLS services to untrusted networks or applying network-level protections to mitigate crafted handshake fragments.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-496x-2f25-59fj
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-63566"]
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6abfeebca43b0b3b89e56606
Added to database: 10/02/2026, 17:49:48 UTC
Last enriched: 10/02/2026, 18:22:50 UTC
Last updated: 10/03/2026, 03:45:56 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.