Receiver crash via undersized Thread1 stack
Published Apr 15, 2026 · Updated Apr 15, 2026
Stack-based buffer overflow in CentSDR commit e407956 allows remote attackers to crash the receiver through unspecified network input. Thread1 receives a fixed 128-byte working area although its worst-case call chain consumes about 224 bytes under certain builds. Exploitation requires a configuration that produces the oversized call chain; public material does not identify the triggering network input.
Summary
What happened
Stack-based buffer overflow in CentSDR commit e407956 allows remote attackers to crash the receiver through unspecified network input. Thread1 receives a fixed 128-byte working area although its worst-case call chain consumes about 224 bytes under certain builds. Exploitation requires a configuration that produces the oversized call chain; public material does not identify the triggering network input.
The record
- CVE
- CVE-2026-30364
- Published
- Apr 15, 2026
- Updated
- Apr 15, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-121, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 15, 2026CVE publishedPublication date reported by the CVE source.
- Apr 15, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
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.
Public exploit references
- CentSDR Thread1 stack-usage proof of conceptproof of concept · demonstrated
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo