{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-33212 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-33212 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-33212 is a high-severity unsafe deserialization vulnerability in NVIDIA NeMo Framework, published on 16 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-33212 and fix it if it is affected.\n\nWhat it is: CVE-2025-33212 is a high-severity unsafe deserialization vulnerability in NVIDIA NeMo Framework, published on 16 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-33212 in the wild and no public exploit code.\n\nAffected product: NVIDIA NeMo Framework. 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-2025-33212/ (Markdown: https://insights.sbomify.com/CVE-2025-33212/index.md)","id":"CVE-2025-33212","markdown":"https://insights.sbomify.com/CVE-2025-33212/index.md","name":"CVE-2025-33212","record":{"aliases":["GHSA-p72j-m23g-j25c"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","privilege_escalation","denial_of_service","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"NVIDIA NeMo Framework","requires_auth":"low_privilege","summary":"Attackers can achieve code execution and privilege escalation by tricking users into loading maliciously crafted files in NVIDIA NeMo Framework.","user_interaction":"required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"nvidia","cpe":[{"product":"nemo","vendor":"nvidia"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"NVIDIA NeMo Framework contains a vulnerability in model loading that could allow an attacker to exploit improper control mechanisms if a user loads a maliciously crafted file. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, 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":false,"headline":"Deserialization in NeMo Framework","id":"CVE-2025-33212","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Deserialization in Merlin Transformers4Rec","id":"CVE-2025-33213"},"packages":[],"prev":{"headline":"Denial of service in Triton Inference Server","id":"CVE-2025-33211"},"products":["NeMo Framework"],"published":"2025-12-16","related":[{"cvss_score":8.6,"headline":"Denial of service in NeMo","id":"CVE-2024-0081","kev_date_added":null,"published":"2024-04-05"},{"cvss_score":8,"headline":"NVIDIA NeMo Framework contains a vulnerability where malicious data could cause remote code execution","id":"CVE-2025-33245","kev_date_added":null,"published":"2026-02-18"},{"cvss_score":7.8,"headline":"Command injection in NeMo Framework","id":"CVE-2026-24252","kev_date_added":null,"published":"2026-07-27"},{"cvss_score":7.8,"headline":"Code injection in NeMo Framework","id":"CVE-2026-24155","kev_date_added":null,"published":"2026-06-16"},{"cvss_score":7.8,"headline":"Deserialization in NeMo Framework","id":"CVE-2026-24228","kev_date_added":null,"published":"2026-06-16"},{"cvss_score":7.8,"headline":"NVIDIA NeMo Framework contains an RCE vulnerability in checkpoint loading","id":"CVE-2026-24157","kev_date_added":null,"published":"2026-03-24"},{"cvss_score":7.8,"headline":"NVIDIA NeMo Framework contains a vulnerability leading to Remote Code Execution","id":"CVE-2026-24159","kev_date_added":null,"published":"2026-03-24"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["NVIDIA"]},"summary":"Attackers can achieve code execution and privilege escalation by tricking users into loading maliciously crafted files in NVIDIA NeMo Framework.","url":"https://insights.sbomify.com/CVE-2025-33212/"}