Quick answers
- Is CVE-2026-49121 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49121 being exploited in the wild.
- How severe is CVE-2026-49121?
- High severity, with a CVSS score of 8.1, published 1 June 2026.
- Which products and versions are affected?
- Amd AI Tensor Engine for ROCm through 0.1.14.
- Is there a fix for CVE-2026-49121?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-49121 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-49121?
- Check whether you run Amd AI Tensor Engine for ROCm at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A remote code execution vulnerability exists in AITER versions up to and including 0.1.14 within the MessageQueue.recv() function in shm_broadcast.py. The vulnerability is caused by the use of the insecure 'pickle' library to deserialize data received from a ZeroMQ (ZMQ) SUB socket without any authentication, HMAC signing, or format validation. An attacker who can reach the writer XPUB endpoint on the cluster network, or who can supply a forged Handle with a malicious remote_subscribe_addr, can deliver a crafted pickle payload. This payload is executed with the privileges of the inference worker process across all remote reader workers. While the attack requires network access to the cluster's internal communication ports, it requires no prior authentication.
Affected products
- AMD AI Tensor Engine for ROCm (AITER) through 0.1.14
Timeline
- 2026-05-13: other: Vulnerability identified as a known issue in project newsletter draft
- 2026-06-01: disclosed: Vulnerability disclosed by VulnCheck
- 2026-06-01: advisory: CVE-2026-49121 published