VSOMEIP · CVE-2026-91141 · Other
NO FIX YET
vsomeip, a SOME/IP middleware library used in automotive and embedded systems, trusts a length field in incoming TCP packets. A remote attacker can send a small packet declaring a huge length, making the service allocate large memory and get killed or exhaust host memory.
first public Nov 12, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Systems running vsomeip in its default configuration with TCP reachable from the network are exposed, per the NVD description. Systems that do not run vsomeip, or that restrict its TCP port, are not described as affected. The sources do not list affected versions or a configuration check.
Not affected if tcp-port-not-exposed, vsomeip-not-used
Who cares automotive, embedded, some-ip, vsomeip
Unknown from the sources.
No fix yet, per the sources.
A vulnerability in the default configuration of vsomeip allows a remote, unauthenticated attacker to trigger massive memory allocations by sending a small TCP packet with a large, attacker-declared SOME/IP length field. This can lead to immediate service termination via OOM-kill on memory-constrained systems or total host memory exhaustion through repeated connections.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.