R1 and R2 now run one software stack. Gen 1 R1 owners get cloud-assisted voice, while local AI processing stays with R2 and Gen 2 R1 hardware.
vsomeip flaw lets one 16-byte message crash car middleware
EditorialBy TrustList Editorial
CERT/CC's note on CVE-2026-91141 covers vsomeip 3.7.3 and below. The fix, release 3.7.4, has been out since July, so the risk now sits in ECU builds that never picked it up.
- Automotive
- Software-Defined Vehicles
- Connected Cars
- Embedded Software Development
- +2 more
About vsomeip flaw lets one 16-byte message crash car middleware
vsomeip flaw lets one 16-byte message crash car middleware
26 October 2026: A flaw in vsomeip, COVESA's open-source implementation of the SOME/IP middleware that electronic control units in cars use to talk to each other, lets an unauthenticated peer make a service allocate up to about 4 GB of memory with a single short message. Tracked as CVE-2026-91141, it affects vsomeip 3.7.3 and earlier in their default configuration and is fixed in release 3.7.4. CERT/CC has now published a note on it, which Japan's JVN relayed a day later.
Not yet independently verified. CERT/CC and COVESA give no CVSS score; the reporter's public issue scores it 4.6 Medium with physical access to the vehicle network, which is the reporter's own assessment. Which carmakers or suppliers ship the affected versions is not public. We will update this when it can be confirmed, and remove this note.
Update, 11 November 2026: The reporter's public issue #1009 scores the flaw 4.6 (Medium) under CVSS 3.1, with a physical attack vector, meaning access to the in-vehicle network, and availability as the only impact. That is the reporter's own assessment: CERT/CC's note still gives no score, and NVD has no record yet.
A length field trusted before the bytes arrive
Every SOME/IP message starts with a 16-byte header carrying a 32-bit length. On reliable (TCP) endpoints, vsomeip grew its receive buffer to whatever size that field declared before checking that the bytes had actually arrived, and by default no size limit applies to reliable endpoints. A freshly accepted connection reaches this code on its first message, so no valid service, credentials or SOME/IP authentication are needed. The client side behaves the same way, so a malicious server can attack the clients that connect to it.
CERT/CC's test shows the effect: a service capped at 1.5 GB of memory was killed by the out-of-memory handler after one 16-byte message claiming a 3 GB payload. On a machine with plenty of memory the allocation is freed when the connection closes, so a lasting denial of service needs connections to be held open or repeated.
Fixed in July, published in October
The bug was reported publicly as issue #1009 on 26 February and fixed in vsomeip 3.7.4, released on 6 July. The fix replaces the unlimited compile-time default with a ceiling of 10 MiB (DEFAULT_MAX_MESSAGE_SIZE), so oversized lengths are refused even where no limit is configured, and adds a regression test. CERT/CC notified COVESA on 13 July and lists its status as unknown, with no vendor statement.
Because automotive software is pinned to a version for a vehicle programme and updated slowly, the useful question is not whether a fix exists but whether it reached the build in a given ECU, gateway, test bench or simulator.
What integrators and test labs should do
- Upgrade to vsomeip 3.7.4 or later.
- Where an upgrade has to wait, set
max-payload-size-reliable, or the per-service reliable message-size limit, to a value that suits the service; endpoints with a limit configured are not affected. - Keep reliable SOME/IP endpoints on isolated in-vehicle or lab networks, allow only known peers, and never expose them to external networks.
- Watch for unexplained memory growth in services with reliable endpoints and for repeated inbound TCP connections to SOME/IP ports.
The note credits Jaafer Rahmani with the report. It does not name affected vehicles or suppliers, and none has published its own advisory so far.
Sources
- CERT/CC: Vulnerability Note VU#128947, vsomeip unbounded memory allocation (CVE-2026-91141), 26 October 2026
- COVESA vsomeip on GitHub: release 3.7.4, 6 July 2026
- JVN: JVNVU#90363302 (Japanese relay of VU#128947), 27 October 2026
- COVESA vsomeip on GitHub: issue #1009 (read 11 November 2026), 11 November 2026
Categories & features
- Automotive
- Software-Defined Vehicles
- Connected Cars
- Embedded Software Development
- Vulnerability Management
- Patch Management
TrustList Weekly
The week in software and IT, in one email
The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.
You may be interested in
Settlement led by Washington and Oregon requires affirmative express consent before GM collects or shares driving and location data, plus privacy assessments and dealer training.
MIIT is consulting until 19 December on five mandatory national standards, including Automobile Data Security Requirements and safety rules for parking assistance and automated parking in connected cars.
The system pairs the EyeQ6L chip with crowdsourced road maps that Mobileye says cover more than 95% of public roads in the US and Europe.
The proposal also drops turn signal, hazard and beam switch rules for vehicles with no steering wheel or pedals. Comments close on 25 November 2026, and NHTSA wants any final rule to take effect at once.
Mercedes-Benz invested in Wayve's Series D earlier in 2026. Customers should see the system in cars within two years, using no HD maps and no geofences.
Pre-registration opens in June. Around one million MEB-platform cars in Europe are technically ready for bidirectional charging, and the smart meter is expected within eight to ten weeks.
At GTC Berlin NVIDIA named Volvo Cars, Mercedes-Benz, Bolt, Einride and others building on its driving platform, and launched Halos SAFE to turn testing into traceable safety evidence.
More on TrustList
Everything here links back to the same verified catalogue. Pick your next stop.
- More AutomotiveThe ranking for this subject
- CompaniesAgencies, consultancies and IT service providers, ranked by verified reviews.
- ProductsSoftware and SaaS with pricing, features, integrations and alternatives.
- AwardsAnnual recognition decided by verified reviews and an independent jury.
- LaunchesNew products and releases, voted up by the community every day.
- AI ModelsBenchmark scores and community ratings for every major model.
- RequestsBuyers describe what they need; vendors respond directly.
- PeopleReviewers, authors and makers with public profiles.
- ComparePut up to four listings side by side before you shortlist.