CVE-2026-91141VulnerabilityPublished 13 Nov 2026

Untitled threat

Source GCVE Database

Compare

Authoritative record:CVE-2026-91141· High

Not known to be exploited : upgrade to 3.7.4 soon.

Data as of 13 Nov 2026, 01:10 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in 3.7.4

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-vvxx-jj9c-53w8

What to do

Upgrade vSomeIp to 3.7.4.

Affected software

Product	Affected	Fixed in
COVESAvSomeIp	Affected >=3.6.1 <3.7.4	Fixed in 3.7.4

AI-suggested

If you cannot patch yet, consider restricting network access to vsomeip services or implementing network-level protections to limit malformed TCP packets with suspicious SOME/IP length fields.

Description

A vulnerability in the default configuration of vsomeip allows a remote, unauthenticated attacker to cause excessive memory allocation by sending a small TCP packet with a large SOME/IP length field. This can result in immediate service termination due to out-of-memory (OOM) conditions on memory-limited systems or complete host memory exhaustion if connections are repeatedly made.

Impact

The impact is denial of service through resource exhaustion. On memory-constrained systems, the vsomeip service can be terminated immediately by the operating system's OOM-killer. On systems with more memory, repeated exploitation can exhaust all host memory, potentially affecting other services and system stability.

Summary

The vulnerability in vsomeip arises from improper handling of the SOME/IP length field in TCP packets. An attacker can send a small packet declaring a large length, causing the system to allocate massive amounts of memory. This leads to denial of service through OOM-kill or total memory exhaustion on the host, impacting availability. The attack requires no authentication and can be triggered remotely against the default configuration of vsomeip.

References

Community reviews

Loading reviews…