Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Sun, 04 Oct 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Legion Of The Bouncy Castle Inc.
Legion Of The Bouncy Castle Inc. bc-csharp |
|
| Vendors & Products |
Legion Of The Bouncy Castle Inc.
Legion Of The Bouncy Castle Inc. bc-csharp |
Sat, 03 Oct 2026 06:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 02 Oct 2026 07:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | DTLS handshake reassembler allocates buffer from unchecked 24-bit length | |
| Weaknesses | CWE-789 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: bcorg
Published:
Updated: 2026-10-02T18:08:57.485Z
Reserved: 2026-07-16T23:48:46.075Z
Link: CVE-2026-63566
Updated: 2026-10-02T18:08:43.262Z
Status : Awaiting Analysis
Published: 2026-10-02T07:16:36.973
Modified: 2026-10-02T18:17:04.750
Link: CVE-2026-63566
No data.
OpenCVE Enrichment
Updated: 2026-10-04T20:55:54Z