Loading story…
NVIDIA disclosed CVE-2026-24254, a critical out-of-bounds write vulnerability in NVIDIA Dynamo for Linux affecting the multimodal serving topology. The flaw impacts versions 0 through v1.1.0 and carries a CVSS v3.1 score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating that it can be exploited remotely without privileges or user interaction.
Successful exploitation could lead to remote code execution, privilege escalation, data tampering, denial of service, and information disclosure. NVIDIA published the issue as part of Security Bulletin 5842, which includes bulletin artifacts and references multiple Dynamo-related CVEs; available metadata indicates no known exploitation so far, while CISA SSVC data flags the bug as automatable with total technical impact.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
3 events from the most recent confirmed update back to the earliest known activity.
On the same day, the CVE-2026-24254 record was modified to add SSVC information. The added CISA-coordinated assessment marked exploitation as none, automatable as yes, and technical impact as total.
CVE-2026-24254 was published as a critical out-of-bounds write vulnerability in NVIDIA Dynamo for Linux's multimodal serving topology. The record states that versions 0 through v1.1.0 are affected and that exploitation could enable code execution, privilege escalation, data tampering, denial of service, and information disclosure.
NVIDIA published product-security bulletin 5842, titled "Security Bulletin: NVIDIA Dynamo - August 2026," in its public repository. The bulletin directory included CSAF, Markdown, checksum files, and MITRE-format CVE JSON files covering CVE-2026-24254 and related Dynamo vulnerabilities.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
3 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcegithub.com
Open sourcecve.org
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
NVIDIA disclosed Security Bulletin **5865** for **NVIDIA Triton Inference Server**, publishing advisory materials and associated MITRE-format CVE records for five vulnerabilities: `CVE-2026-47606`, `CVE-2026-47627`, `CVE-2026-47628`, `CVE-2026-47629`, and `CVE-2026-47630`. The bulletin was released through NVIDIA's product-security repository with CSAF, Markdown, checksum, and CVE JSON files, indicating a coordinated vendor advisory covering multiple issues in the inference-serving platform. The most severe issue publicly detailed is **`CVE-2026-47627`**, a **critical** path traversal vulnerability (`CWE-22`) affecting **NVIDIA Triton Inference Server on Linux** in versions **0.0 through 26.05**. The CVE record assigns a **CVSS v3.1 score of 9.8** with vector `AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, and NVIDIA states that successful exploitation could lead to **denial of service**.
Aug 18, 2026
NVIDIA disclosed **CVE-2026-47483**, a vulnerability in **DCGM** and **DCGM Exporter** that allows unauthenticated attackers to abuse exposed `/debug/pprof` diagnostic endpoints and trigger uncontrolled resource consumption. By sending many concurrent profiling requests, an attacker can exhaust CPU, memory, and file descriptors, causing the exporter to become unresponsive or crash. The issue affects all platforms within the impacted version ranges and carries a CVSS v3.1 score reflecting **high availability impact** with possible limited information disclosure. Security advisories warn that exploitation can disrupt GPU monitoring, telemetry, and alerting, and prolonged abuse may also destabilize the host system. The exposed profiling interface may leak limited diagnostic data, including internal stack traces. Public guidance says there is **no known exploitation** so far, but the flaw is considered automatable; defenders are urged to deploy NVIDIA’s patched version and reduce exposure of the diagnostic endpoints through firewalling, authentication, rate limiting, and network isolation.
Jul 30, 2026
NVIDIA issued security updates for multiple products across its AI and enterprise software stack, fixing vulnerabilities that could allow **remote code execution**, denial of service, privilege escalation, data tampering, and information disclosure. The most severe issue disclosed in its broader March advisories was `CVE-2025-33244` in **NVIDIA Apex**, a widely used PyTorch extension for mixed-precision and distributed training. High-severity flaws were also addressed in **Triton Inference Server**, **Megatron LM**, **NeMo Framework**, and **Model Optimizer**, with NVIDIA warning that exploitation could disrupt AI workloads, expose sensitive training data, or enable unauthorized access. Medium-severity issues were additionally listed in **VIRTIO-Net**, **SNAP4**, and **B300 MCU**. NVIDIA later released urgent fixes for **TensorRT-LLM** and **Isaac Launchable**, including TensorRT-LLM deserialization flaws in MPI server and RPC testing components that could lead to RCE, data manipulation, information disclosure, or service outages. It also patched a Linux issue in Isaac Launchable involving sensitive information sent in clear text, creating risks of privilege escalation and system disruption. NVIDIA advised customers to upgrade **TensorRT-LLM** to `1.2.1` or later, and said organizations running multi-GPU deployments should use: ```bash trtllm-llmapi-launch ``` to reduce network exposure. The company has also begun publishing PSIRT bulletins on GitHub in Markdown and CSAF formats to support automated vulnerability management and faster remediation.
Jun 29, 2026