ROCm aiter up to 0.1.14 Writer XPUB Endpoint shm_broadcast.py MessageQueue.recv deserialization

Summaryinfo

A vulnerability, which was classified as problematic, has been found in ROCm aiter up to 0.1.14. The affected element is the function MessageQueue.recv of the file shm_broadcast.py of the component Writer XPUB Endpoint. Performing a manipulation results in deserialization. This vulnerability is known as CVE-2026-49121. Remote exploitation of the attack is possible. No exploit is available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability, which was classified as problematic, was found in ROCm aiter up to 0.1.14. This affects the function MessageQueue.recv of the file shm_broadcast.py of the component Writer XPUB Endpoint. The manipulation with an unknown input leads to a deserialization vulnerability. CWE is classifying the issue as CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was published by Yu Sun as 3076. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-49121 since 05/27/2026. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.

Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• ROCm

Name

• aiter

Version

• 0.1.0
• 0.1.1
• 0.1.2
• 0.1.3
• 0.1.4
• 0.1.5
• 0.1.6
• 0.1.7
• 0.1.8
• 0.1.9
• 0.1.10
• 0.1.11
• 0.1.12
• 0.1.13
• 0.1.14

Website

• Product: https://github.com/ROCm/aiter/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion