{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-53805 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-53805 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-53805 is a critical unsafe deserialization vulnerability in nv-tlabs GEN3C, published on 17 Jun 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-53805 and fix it if it is affected.\n\nWhat it is: CVE-2026-53805 is a critical unsafe deserialization vulnerability in nv-tlabs GEN3C, published on 17 Jun 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-53805 in the wild and no public exploit code.\n\nAffected product: nv-tlabs GEN3C. 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-53805/ (Markdown: https://insights.sbomify.com/CVE-2026-53805/index.md)","id":"CVE-2026-53805","markdown":"https://insights.sbomify.com/CVE-2026-53805/index.md","name":"CVE-2026-53805","record":{"aliases":["GHSA-478c-rj3v-9229"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"NVIDIA GEN3C inference API","requires_auth":"none","summary":"Unauthenticated attackers can achieve remote code execution on NVIDIA GEN3C inference servers by sending malicious pickle payloads to specific API endpoints.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"NVIDIA Spatial Intelligence Lab's (SIL) GEN3C contains an unauthenticated remote code execution vulnerability in the inference API server where the /request-inference and /seed-model endpoints deserialize raw HTTP request bodies using Python's pickle.loads() without authentication or input validation. Attackers can supply a crafted payload containing a __reduce__ gadget to the inference API port to achieve remote code execution as the inference process.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-07-13","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-07-13T07:29:43Z","kind":"github_poc","ref":"https://github.com/HORKimhab/CVE-2026-53805","stars":0,"title":"CVE-2026-53805 - Draft"}],"tier":"poc_unverified"},"has_fix":false,"headline":"NVIDIA SIL GEN3C Unauthenticated RCE via Pickle Deserialization in Inference API","id":"CVE-2026-53805","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"OpenClaw \u003c 2026.5.12 - Shell Option Parsing Bypass in Exec Revalidation","id":"CVE-2026-53806"},"packages":[],"prev":{"headline":"OTRS Community Edition OS Command Injection via PGP Configuration","id":"CVE-2026-53804"},"products":["GEN3C"],"published":"2026-06-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-14","vendors":["nv-tlabs"]},"summary":"Unauthenticated attackers can achieve remote code execution on NVIDIA GEN3C inference servers by sending malicious pickle payloads to specific API endpoints.","url":"https://insights.sbomify.com/CVE-2026-53805/"}