CVE-2026-92613
Received Received - Intake

Memory Corruption in Eclipse iceoryx-rs

Vulnerability report for CVE-2026-92613, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-19

Last updated on: 2026-11-19

Assigner: Eclipse Foundation

Description

In Eclipse iceoryx-rs, versions 0.0.11 to 0.0.13 and 0.1.0 as well as on the latest main branch. `SampleReceiver::<T>::take()` and `Sample::<T>::deref()` are safe functions that hand the caller a `&T` pointing at a chunk written by another iceoryx process, but the subscriber path neither requires `T: ShmSend` nor verifies that the received chunk is at least `size_of::<T>()` bytes / `align_of::<T>()`-aligned. A peer process that publishes an undersized chunk, or any chunk at all when the subscriber chose a pointer-bearing `T`, drives a `#![forbid(unsafe_code)]` subscriber into out-of-bounds reads of adjacent shared-memory chunks or dereference of a publisher-controlled pointer. Resolution: It will not be fixed since this is a known limitation in iceoryx as it is the users responsibility to specify the same data type on sender and receiver side. [iceoryx2](https://github.com/eclipse-iceoryx/iceoryx2) is the successor of iceoryx-rs where the API is designed to prevent this by default. It is strongly recommended to migrate to iceoryx2 which is actively maintained and receives security support. The iceoryx-rs package has officially reached End-of-life and will not receive any features, bugfixes or security fixes.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-19
Last Modified
2026-11-19
Generated
2026-11-20
AI Q&A
2026-11-19
EPSS Evaluated
2026-11-19
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Eclipse Foundation Eclipse iceoryxβ„’ From 0.0.11 (inc) to 0.1.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-843 The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.
CWE-125 The product reads data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects Eclipse iceoryx-rs versions 0.0.11 to 0.0.13 and 0.1.0. It involves safe subscriber API functions that return a reference to shared-memory data without validating the data type or size. A malicious peer can publish undersized or misaligned data, causing out-of-bounds reads or dereferencing of arbitrary pointers in a subscriber marked as safe.

Detection Guidance

This vulnerability cannot be detected via standard network or system commands as it requires manual code review and runtime analysis. Focus on verifying if your application uses iceoryx-rs versions 0.0.11 to 0.0.13, 0.1.0, or the latest main branch. Check for unsafe code patterns involving SampleReceiver::<T>::take() or Sample::<T>::deref().

Impact Analysis

An attacker with publish rights on the same host could exploit this to crash the subscriber process or corrupt memory. Since the subscriber uses safe Rust code, this occurs without explicit unsafe blocks, making it harder to detect. The impact is limited to local processes sharing memory.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR or HIPAA as it is a type safety issue in a Rust shared-memory library. However, if exploited, it could lead to memory corruption or arbitrary code execution, which may indirectly impact systems handling sensitive data under these regulations.

Mitigation Strategies

Immediately migrate from iceoryx-rs to iceoryx2, as it addresses this issue by default. If migration is not possible, ensure all sender and receiver processes use identical data types and enforce ShmSend trait bounds. Avoid using pointer-bearing types in shared memory.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-92613. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...