PatchSiren cyber security CVE debrief
CVE-2026-65104 NVIDIA CVE debrief
NVIDIA Megatron-LM vulnerability allows data tampering and partial information disclosure due to hash collisions in the inference cache. This vulnerability affects NVIDIA Megatron-LM deployments, which may be exposed to potential data tampering and partial information disclosure. Defenders should assess exposure, prioritize verification of affected versions, and monitor for potential data tampering. The vulnerability has a CVSS score of 7.1 and is considered HIGH severity. The CVE record was published on 2026-10-13T13:05:46.417Z and has not been modified since then.
- Vendor
- NVIDIA
- Product
- Megatron-LM
- CVSS
- HIGH 7.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-13
- Original CVE updated
- 2026-10-13
- Advisory published
- 2026-10-13
- Advisory updated
- 2026-10-13
Who should care
Defenders of Megatron-LM deployments, security teams, and vulnerability management teams should assess exposure and prioritize verification of affected versions. Operators of affected platforms and systems should monitor for potential data tampering and review compensating controls for exposed systems.
Why it matters
CVE-2026-65104 allows data tampering and partial information disclosure in NVIDIA Megatron-LM deployments due to hash collisions in the inference cache. Defenders should assess exposure, prioritize verification of affected versions, and monitor for potential data tampering.
- Data tampering and partial information disclosure possible
- Need to verify affected versions and assess exposure
- Monitoring for potential data tampering required
Technical summary
NVIDIA Megatron-LM for all platforms contains a vulnerability in inference, where an attacker could cause hash collisions in the cache used for inference requests. This vulnerability may lead to data tampering and partial information disclosure. The vulnerability affects NVIDIA Megatron-LM deployments and has a CVSS score of 7.1. Defenders should assess exposure and prioritize verification of affected versions. The CVE record and NVD detail provide source-grounded information on the vulnerability, but may not cover all affected versions or platforms.
Defensive priority
Assess exposure of Megatron-LM deployments, prioritize verification of affected versions, and monitor for potential data tampering.
Recommended defensive actions
- Assess exposure of Megatron-LM deployments
- Prioritize verification of affected versions
- Monitor for potential data tampering
- Review compensating controls for exposed systems
- Check relevant monitoring, detection, and logs for exposed assets
- Track exceptions, retest remediated assets
- Confirm whether affected product deployments exist in managed environments
Evidence notes
Official CVE Program record and NVD vulnerability detail provide information on the vulnerability. NVIDIA's canonical source confirms affected product. The CVE record and NVD detail provide source-grounded information on the vulnerability, but may not cover all affected versions or platforms. Defenders should verify affected versions and assess exposure.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-65104 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-65104
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-65104 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-65104
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
CVE-2026-65104
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/65xxx/CVE-2026-65104.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://github.com/NVIDIA/product-security/tree/main/2026/5881
Supplemental source
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.