GPU VulnDB

Database/AI/ML frameworks & serving

NVIDIA Megatron-LM: hash collisions in the inference cache let one request's data reach another

CVSS 7.1CVE-2026-65104AI/ML frameworks & servingcurated

Impact

The cache Megatron-LM keeps for inference requests can be made to collide, so a crafted request is served content keyed to a different one. NVIDIA scores this with a changed scope and network vector (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:H/A:N), meaning the effect crosses the boundary of the component itself - on a shared endpoint that is one tenant's request influencing or partially reading another's. Integrity is the high half: responses can be tampered with, with only partial disclosure. Attack complexity is high, so this is not a casual exploit, but on a multi-tenant inference endpoint it is a cross-tenant issue rather than a local one.

Who can reach it

Network, authenticated low-privileged user, no interaction - any client able to submit inference requests to a Megatron-LM endpoint that caches them.

What to do

Upgrade Megatron-LM to the fixed version in NVIDIA bulletin 2026/5881 and restart the inference service; the same upgrade covers the checkpoint-loading ids in that bulletin. If you cannot patch immediately, disabling or partitioning the inference request cache per tenant removes the shared-state precondition. The NVD record does not name a fixed version.

References

Related entries

All AI/ML frameworks & serving entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.