Service termination via unbounded receive-buffer allocation
Published Nov 12, 2026 · Updated Nov 12, 2026
Memory exhaustion in COVESA vSomeIP 3.7.3 and earlier allows remote attackers to terminate services via crafted TCP messages. Reliable TCP endpoints grow their receive buffers to an untrusted SOME/IP length before receiving the declared bytes. Reachable endpoints with no configured reliable message-size limit require no credentials; allocation triggers OOM termination on constrained hosts or sustained host memory exhaustion through repeated connections.
Summary
What happened
Memory exhaustion in COVESA vSomeIP 3.7.3 and earlier allows remote attackers to terminate services via crafted TCP messages. Reliable TCP endpoints grow their receive buffers to an untrusted SOME/IP length before receiving the declared bytes. Reachable endpoints with no configured reliable message-size limit require no credentials; allocation triggers OOM termination on constrained hosts or sustained host memory exhaustion through repeated connections.
The record
- CVE
- CVE-2026-91141
- Published
- Nov 12, 2026
- Updated
- Nov 12, 2026
- Vendor
- COVESA
- Product
- vSomeIP
- Classifications
- CWE-400, CWE-789, CWE-1284, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 12, 2026CVE publishedPublication date reported by the CVE source.
- Nov 12, 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=v3.6.1 <3.7.4
What conditions does exploitation require?
What is affected?
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.
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.
Contact us