Skip to main content
Menu
CVEs

Eclipse iceoryx out-of-bounds read in shared-memory subscriber

CVE-2026-92613EUVD-2026-129501GHSA-6F8F-G66F-8VFPPublished November 19, 2026, updated

1.0LowCNA
Exploited
Proof of concept public, per CISA
Fix
See vendor advisory
Who is exposed
Not reported

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

Original 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 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 systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

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"}.

Affected versions

cve.now Index

21Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity1/10CVSS 1.0
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 61 if added to CISA KEV
  • Would score about 56 if CISA's SSVC rates exploitation active
  • Would score about 43 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 4

KindSource
Vendor advisory 2Establishes: Affected and fixed versions.
AdvisoryGitHub · eclipse-iceoryx/iceoryx-rs · Advisory GHSA-gq84-237w-c3cw
Linkgitlab.eclipse.org · security/cve-assignment/-/work_items/306
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-92613
RecordNVD · CVE-2026-92613

Questions about CVE-2026-92613

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: cve.now feed data

Which versions are affected by CVE-2026-92613?

Eclipse iceoryx™: from 0.0.11 through 0.1.0.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.