dbcve.org
AiterApplication · Amd

CVE-2026-49121

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-01
Fix available
A fix is available. Upgrade to after 0.1.14 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
AI Tensor Engine for ROCm (AITER) through 0.1.14 contains an unauthenticated remote code execution vulnerability in the MessageQueue.recv() function within shm_broadcast.py that allows unauthenticated remote attackers to execute arbitrary code by sending a malicious pickle payload to a ZMQ SUB socket with no authentication, HMAC, or format validation. Attackers who can reach the writer XPUB endpoint on the cluster network or supply a forged Handle with an attacker-controlled remote_subscribe_addr can deliver a crafted pickle payload that executes arbitrary code simultaneously as the inference worker process on every remote reader worker.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

AI Tensor Engine for ROCm (AITER) through 0.1.14 contains an unauthenticated RCE vulnerability in the MessageQueue.recv() function in shm_broadcast.py. The ZMQ SUB socket accepts pickle payloads without authentication, HMAC verification, or format validation, allowing attackers who can reach the XPUB endpoint or supply a forged Handle with attacker-controlled remote_subscribe_addr to execute arbitrary code on all remote reader workers simultaneously.

MitigationImplement authentication and HMAC verification on ZMQ socket communications, add strict format validation for pickle payloads, and validate Handle remote_subscribe_addr parameters to prevent forgery.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AiterApplication
Affected:<= 0.1.14

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify AITER installation and version
    Run 'pip show aiter' or 'pip list | grep -i aiter' to check if Amd Aiter is installed and what version number is reported
    Affected if The installed version is 0.1.14 or lower
  2. Locate the vulnerable shm_broadcast.py file
    Search for shm_broadcast.py in the AITER installation directory (typically in site-packages/aiter or similar), then verify the MessageQueue.recv() method uses pickle for deserialization
    Affected if The file exists and contains recv() method that deserializes data with pickle without validation
  3. Check ZMQ socket configuration
    Examine the ZMQ XPUB/SUB socket setup in the AITER configuration or source code, look for authentication, HMAC, or format validation on the socket
    Affected if ZMQ sockets are configured without authentication, HMAC verification, or format validation on incoming messages
  4. Determine if XPUB endpoint is network-accessible
    Review network configuration and firewall rules to check if the ZMQ XPUB port is exposed to untrusted networks or accessible without authentication
    Affected if The XPUB endpoint is accessible from untrusted network segments or lacks access controls
  5. Verify pickle deserialization is used
    Search the codebase for 'pickle.loads' or 'pickle.load' calls within the messaging or broadcast modules
    Affected if The code uses pickle for deserializing incoming messages from the ZMQ SUB socket

A user is affected if they have Amd AITER version 0.1.14 or lower installed, with ZMQ sockets configured without authentication using pickle deserialization, and the XPUB endpoint is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 0.1.14
Vendor patch github.com →
Interim mitigation

Implement authentication and HMAC verification on ZMQ socket communications, add strict format validation for pickle payloads, and validate Handle remote_subscribe_addr parameters to prevent forgery.

Recommended fix Moderate confidence

Upgrade to the latest Aiter release beyond version 0.1.14 (verify the fixed version from the merged PR #3170)

  1. Verify the current installed version of Aiter: pip show aiter or pip list | grep aiter
  2. Stop any running Aiter services or inference workers that may be using the vulnerable version
  3. Upgrade to the latest version that includes the fix from PR #3170: pip install --upgrade aiter
  4. Alternatively, pull the specific fixed commit/branch from the repository if pip installation is not available: git pull https://github.com/ROCm/aiter.git and checkout the fixed version
  5. Verify the upgrade was successful: pip show aiter and confirm the version is newer than 0.1.14
  6. Restart all Aiter services and inference workers to load the patched version
  7. If unable to upgrade immediately, configure ZMQ with authentication (e.g., ZAP authentication) and enable HMAC signature validation on the SUB socket to mitigate the deserialization attack vector
Caveat Review release notes for any breaking changes between 0.1.14 and the target version; ensure compatibility with your ROCm version and inference workload dependencies

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Aiter Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-49121 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-49121 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data