Service interruption via unchecked DTLS fragment length
Published Oct 2, 2026 · Updated Oct 2, 2026
Excessive allocation in Bouncy Castle C# .NET DTLS reassembly before 2.7.0 allows remote attackers to exhaust application memory via fragments. The DTLS handshake reassembler allocates a buffer from the untrusted 24-bit message length without checking the peer's maximum handshake message size. The attack requires an application using the library's DTLS client or server implementation; stream TLS is not affected.
Summary
What happened
Excessive allocation in Bouncy Castle C# .NET DTLS reassembly before 2.7.0 allows remote attackers to exhaust application memory via fragments. The DTLS handshake reassembler allocates a buffer from the untrusted 24-bit message length without checking the peer's maximum handshake message size. The attack requires an application using the library's DTLS client or server implementation; stream TLS is not affected.
The record
- CVE
- CVE-2026-63566
- Published
- Oct 2, 2026
- Updated
- Oct 2, 2026
- Vendor
- Legion of the Bouncy Castle Inc.
- Product
- Bouncy Castle C# .NET
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 2, 2026CVE publishedPublication date reported by the CVE source.
- Oct 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.7.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started