{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-24253 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-24253 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-24253 is a high-severity memory corruption vulnerability in NVIDIA Dynamo, published on 4 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-24253 and fix it if it is affected.\n\nWhat it is: CVE-2026-24253 is a high-severity memory corruption vulnerability in NVIDIA Dynamo, published on 4 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-24253 in the wild and no public exploit code.\n\nAffected product: NVIDIA Dynamo. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-24253/ (Markdown: https://insights.sbomify.com/CVE-2026-24253/index.md)","id":"CVE-2026-24253","markdown":"https://insights.sbomify.com/CVE-2026-24253/index.md","name":"CVE-2026-24253","record":{"aliases":["GHSA-5c7q-rvp2-6mxc"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"NVIDIA Dynamo","requires_auth":"none","summary":"An attacker can trigger an out-of-bounds write in NVIDIA Dynamo, causing denial of service and data tampering.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"nvidia","cpe":[{"product":"dynamo","vendor":"nvidia"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"NVIDIA Dynamo for Linux contains a vulnerability where an attacker could cause an out-of-bounds write. A successful exploit of this vulnerability might lead to denial of service and data tampering.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Memory corruption in Dynamo","id":"CVE-2026-24253","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in Dynamo","id":"CVE-2026-24254"},"packages":[],"prev":{"headline":"Command injection in NeMo Framework","id":"CVE-2026-24252"},"products":["Dynamo"],"published":"2026-08-04","related":[{"cvss_score":9.8,"headline":"Memory corruption in Dynamo","id":"CVE-2026-24254","kev_date_added":null,"published":"2026-08-04"},{"cvss_score":8.2,"headline":"Deserialization in Dynamo","id":"CVE-2026-47623","kev_date_added":null,"published":"2026-08-04"},{"cvss_score":7.5,"headline":"Other in Dynamo","id":"CVE-2026-24255","kev_date_added":null,"published":"2026-08-04"},{"cvss_score":7.5,"headline":"Path traversal in Dynamo","id":"CVE-2026-47612","kev_date_added":null,"published":"2026-08-04"},{"cvss_score":7.5,"headline":"Path traversal in Dynamo","id":"CVE-2026-47613","kev_date_added":null,"published":"2026-08-04"},{"cvss_score":7.5,"headline":"Server-side request forgery in Dynamo","id":"CVE-2026-47614","kev_date_added":null,"published":"2026-08-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-04","vendors":["NVIDIA"]},"summary":"An attacker can trigger an out-of-bounds write in NVIDIA Dynamo, causing denial of service and data tampering.","url":"https://insights.sbomify.com/CVE-2026-24253/"}