CVE-2026-53805
Received Received - Intake
BaseFortify

Publication date: 2026-06-17

Last updated on: 2026-06-17

Assigner: VulnCheck

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-17
Last Modified
2026-06-17
Generated
2026-06-18
AI Q&A
2026-06-17
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
nvidia gen3c to db2ffe1 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-502 The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-53805 is a critical security vulnerability in NVIDIA Spatial Intelligence Lab's GEN3C inference API server. The vulnerability arises because the /request-inference and /seed-model endpoints deserialize raw HTTP request bodies using Python's pickle.loads() function without any authentication or input validation.

Since pickle.loads() can execute arbitrary code during deserialization, an attacker can craft a malicious payload containing a __reduce__ gadget and send it to these endpoints. This allows the attacker to achieve unauthenticated remote code execution (RCE) as the inference process.

The vulnerability is classified under CWE-502 (Deserialization of Untrusted Data) and has a high severity with CVSS scores of 9.3 (v4.0) and 9.8 (v3.1).

Impact Analysis

This vulnerability allows an unauthenticated attacker to remotely execute arbitrary code on the server running the GEN3C inference API. Because the vulnerable endpoints do not require authentication or input validation, any attacker with network access to the API port can exploit this flaw.

Successful exploitation could lead to full compromise of the inference process, potentially allowing attackers to execute malicious commands, manipulate data, disrupt services, or gain further access to the underlying system.

This poses a significant security risk, especially in environments where GEN3C is exposed to untrusted networks or users.

Detection Guidance

This vulnerability can be detected by monitoring network traffic for unauthorized or suspicious HTTP requests to the inference API server endpoints /request-inference and /seed-model, which deserialize raw HTTP request bodies using Python's pickle.loads() without authentication.

You can use network inspection tools like curl or netcat to send crafted requests to these endpoints and observe the server's response or behavior.

  • Use curl to test the endpoints: curl -X POST http://<server-ip>:<port>/request-inference -d '<payload>'
  • Use netcat or similar tools to monitor open ports and unexpected incoming connections on the inference API port.

Additionally, checking the server code or version against the fixed commit (db2ffe1) can help confirm if the vulnerable pickle deserialization is present.

Mitigation Strategies

Immediate mitigation involves updating the GEN3C software to the fixed version that replaces unsafe pickle deserialization with a safer serialization method such as JSON or safetensors.

Specifically, apply the patch introduced in commit db2ffe1 and pull requests #62 and #63, which remove pickle.loads() from the inference API endpoints and enforce strict type checking and safe deserialization.

Until the update is applied, restrict network access to the inference API server ports to trusted clients only, and consider disabling or firewalling the /request-inference and /seed-model endpoints to prevent unauthenticated access.

Monitor for suspicious activity and consider implementing additional authentication or input validation layers if possible.

Compliance Impact

The provided context and resources do not contain specific information about how CVE-2026-53805 affects compliance with common standards and regulations such as GDPR or HIPAA.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-53805. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart