Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconObtain low-privilege FLARE credentials
-
DeliveryConnect to target FLARE node endpoint
-
ExploitCraft malicious FOBS-serialized payload
-
InstallSend payload via network to FOBS deserializer
-
C2Trigger unsafe deserialization
-
ExecuteExecute arbitrary Python code
-
ImpactCompromise federated learning infrastructure
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Attacker must possess valid authenticated credentials to a NVIDIA FLARE SDK participant node (CVSS PR:L indicates low-privilege authentication required). The target deployment must use FOBS serialization for inter-node message passing, which is the standard communication mechanism in NVIDIA FLARE federated learning workflows. Exploitation is network-based (AV:N) requiring connectivity to FLARE SDK endpoints that accept FOBS-encoded messages, typically present in any active federated learning project. No user interaction required (UI:N) once network access and authentication are established. This vulnerability is particularly exploitable in multi-organization federated learning scenarios where external partners receive authenticated participant access, as low-privilege credentials from any compromised or malicious participant enable the attack. |
| Impact | This represents a high-severity risk to federated learning deployments using NVIDIA FLARE SDK. The CVSS 8.8 score accurately reflects the critical nature: network-accessible (AV:N), low attack complexity (AC:L), and complete system impact (C:H/I:H/A:H). The only mitigating factor is the low-privilege authentication requirement (PR:L), meaning attackers need valid credentials to a FLARE participant node. However, in federated learning scenarios, multiple external organizations typically have authenticated access, significantly expanding the attack surface. EPSS data not provided, preventing probabilistic exploitation assessment. No CISA KEV listing indicates no confirmed active exploitation, though absence from KEV does not eliminate risk given NVIDIA's prominence as a target. The automatable nature (no user interaction required) and RCE impact make this a priority patch candidate for any organization running NVIDIA FLARE in production, especially in multi-tenant or cross-organizational federated learning environments where participants may not be fully trusted. |
| Exploit ScenarioDerived | An authenticated attacker with low-privilege credentials to a NVIDIA FLARE federated learning participant node crafts a malicious FOBS-encoded message containing serialized Python objects designed to execute code during deserialization. The attacker transmits this payload over the network to a target FLARE node, which deserializes the untrusted data without validation. During deserialization, the malicious objects invoke arbitrary methods, allowing the attacker to execute code with the privileges of the FLARE SDK process, potentially gaining complete control of the federated learning infrastructure and access to sensitive training data or model parameters. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 28, 2026
Remote code execution in NVIDIA FLARE SDK allows authenticated attackers to execute arbitrary code by sending maliciously crafted FOBS-encoded messages that exploit unsafe deserialization in the FOBS component. The vulnerability affects federated learning deployments where NVIDIA FLARE SDK processes messages from low-privileged authenticated users, enabling complete system compromise with high impact to confidentiality, integrity, and availability. No active exploitation confirmed (not in CISA KEV) and public exploit status unknown at time of analysis.
RemediationAI
Apply the security update detailed in NVIDIA Security Bulletin 5819 available at https://nvidia.custhelp.com/app/answers/detail/a_id/5819. Upgrade NVIDIA FLARE SDK to the patched version specified in the bulletin immediately. As interim mitigation until patching is feasible, restrict network access to FLARE SDK endpoints using firewall rules to allow only explicitly trusted federated learning participant IP addresses, reducing the pool of potential authenticated attackers. Implement additional authentication layers such as mutual TLS with certificate pinning for FLARE node-to-node communication to raise the authentication barrier beyond low-privilege credentials. Monitor FOBS message traffic for anomalous patterns such as unusually large serialized payloads or unexpected object types, though sophisticated attacks may evade signature-based detection. Note that access restrictions trade off the flexibility of federated learning participant onboarding against security, requiring manual IP allowlisting for each new participant.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
NVIDIA FLARE (Federated Learning Application Runtime Environment) SDK is a framework for privacy-preserving collaborative machine learning across distributed participants. FOBS (FLARE OBject Serialization) is NVIDIA's custom serialization mechanism for efficiently encoding and transmitting objects between federated learning nodes. This vulnerability stems from CWE-502 (Deserialization of Untrusted Data), where the FOBS deserializer fails to properly validate incoming serialized data before reconstructing objects. When malicious FOBS-encoded messages are processed, attackers can instantiate arbitrary Python objects and invoke methods during deserialization, leading to remote code execution. This class of vulnerability is particularly dangerous in distributed computing frameworks where nodes regularly exchange serialized data structures.
Know when Flare Sdk gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from Vendor (nvidia) · only source for this CVE.
CVSS VectorVendor: nvidia
DescriptionCVE.org
NVIDIA FLARE SDK contains a vulnerability in FOBS, where an attacker may cause deserialization of untrusted data by sending a malicious FOBS- encoded message. A successful exploit of this vulnerability might lead to code execution.
Executive ViewAI
NVIDIA FLARE SDK versions prior to the fix release contain a remote code execution vulnerability (CVSS 8.8) affecting federated learning infrastructure. Authenticated users can exploit unsafe deserialization in the FOBS messaging component to achieve arbitrary code execution and full system compromise. Organizations deploying FLARE for distributed machine learning should immediately assess their exposure and implement mitigations, as no patch is currently available.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict network access to FLARE deployments using firewall rules and VPN requirements-limit message handling to trusted internal subnets only; (2) Implement strict authentication controls with multi-factor authentication for all FLARE user accounts; (3) Disable or isolate FOBS deserialization processing where operationally feasible; (4) Enable comprehensive audit logging and real-time monitoring of FLARE message traffic for anomalous deserialization patterns; (5) Run FLARE services with minimal required privileges and in isolated containers with restricted resource access; (6) Monitor vendor advisories and CISA alerts for patch release notifications.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Authentication bypass in NVIDIA NVFlare Dashboard allows remote unauthenticated attackers to escalate privileges through
NVIDIA Flare SDK is vulnerable to path traversal via improper input validation, allowing authenticated remote attackers
EUVD-2026-26076
NVD
CVE.org
EPSS
Vulnrichment
GitHub PoC
Exploit-DB