CVE Feed
1.0 Low

In Eclipse iceoryx-rs, versions 0.0.11 to 0.0.13 and 0.1.0 as well as on the latest main branch.

CVE-2026-92613

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:: ::take() and Sample:: ::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 sizeof:: () bytes / alignof:: ()-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(unsafecode)] 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.

Assessment

CVSS
1 (v4.0)
Severity
Low
Known exploited
Not listed in CISA KEV
Exploit availability
Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published
19 November 2026
Last updated
19 November 2026
Assigner
eclipse

CVSS vectorCVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

At the source

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept
Before you submit *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-92613