Skip to main content

NVIDIA Flare SDK CVE-2026-24204

| EUVDEUVD-2026-26077 MEDIUM
Improper Input Validation (CWE-20)
2026-04-28 nvidia
6.5
CVSS 3.1 · Vendor: nvidia
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Obtain valid Flare SDK credentials
  2. Delivery
    Authenticate to SDK interface
  3. Exploit
    Craft request with path traversal payload
  4. Install
    Submit to file access endpoint
  5. C2
    SDK processes unsanitized path
  6. Execute
    Read unauthorized file
  7. Impact
    Exfiltrate sensitive data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
Exploitation Conditions

Exploitation requires valid authenticated credentials to access the NVIDIA Flare SDK interface or API (PR:L in CVSS vector). The attacker must identify a file parameter or API endpoint that processes file paths without proper validation. No special SDK configuration or non-default setup is explicitly mentioned as required. The vulnerability is accessible remotely over the network (AV:N) without user interaction (UI:N), but only after authentication is established. The vulnerability does NOT require elevated privileges beyond standard user access.

Impact

CVSS score of 6.5 (Medium) with network attack vector and low complexity reflects moderate risk. The requirement for authenticated access (PR:L) significantly limits real-world exposure compared to unauthenticated remote vulnerabilities. EPSS data is not available for independent validation of exploitation probability. The confidentiality impact is rated high (C:H), meaning successful exploitation grants access to sensitive data, but integrity and availability are unaffected (I:N/A:N). The confined scope (S:U) indicates the vulnerability does not breach security boundaries of other systems. No KEV listing or POC identified, suggesting this is not currently exploited in the wild at scale. For organizations using Flare in trusted environments with limited user access, risk is lower; for multi-tenant or open-access deployments, risk is higher. The combination of mandatory authentication and information-disclosure-only impact makes this a lower priority than remote unauthenticated code execution vulnerabilities, but still requires remediation in security-sensitive deployments.

Exploit ScenarioDerived

An authenticated user with access to a Flare SDK instance crafts a malicious request with path traversal sequences in a file parameter (e.g., '../../../etc/passwd'). The SDK fails to validate or sanitize the input, processes it as-is, and returns the contents of the sensitive file outside the intended directory. The attacker gains access to configuration files, credentials, model data, or other confidential information stored on the server.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 28, 2026

NVIDIA Flare SDK is vulnerable to path traversal via improper input validation, allowing authenticated remote attackers to disclose sensitive information. The vulnerability affects all versions of the SDK and requires valid user credentials to exploit, making it a moderate-risk issue for organizations using Flare in multi-user environments. No public exploit code or active exploitation has been identified.

RemediationAI

Consult NVIDIA's official security advisory at https://nvidia.custhelp.com/app/answers/detail/a_id/5819 for the exact patched version. Once a patch is released, upgrade Flare SDK to the fixed version immediately. As an interim mitigation for organizations unable to patch quickly, implement strict input validation on all file path parameters by employing allowlist-based path resolution (only permit access to explicitly approved directories), use chroot or containerization to limit file system scope accessible to the Flare process, restrict Flare SDK deployment to trusted networks with strict access controls, and audit access logs for unusual file operations. These compensating controls reduce but do not eliminate risk and should be considered temporary until patching is possible.

Affected VersionsENISA

FLARE SDK All versions prior to 2.7.2

Affected Packages

euvd flare_sdk_all_versions_prior_to no fix

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 SDK is a federated learning framework that enables collaborative machine learning across distributed data sources. The vulnerability stems from CWE-20 (Improper Input Validation), specifically a path traversal flaw where user-supplied input is not properly validated before being used in file system operations. An attacker with valid credentials can manipulate file path parameters (such as directory or file name inputs) to traverse beyond intended boundaries (e.g., using '../' sequences) and access files outside the intended directory structure. This is a common pattern in web and distributed applications where input sanitization is insufficient.

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

Vendor (nvidia) PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Primary rating from Vendor (nvidia) · only source for this CVE.

CVSS VectorVendor: nvidia

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

DescriptionCVE.org

NVIDIA Flare SDK contains a vulnerability where an Attacker may cause an Improper Input Validation by path traversing. A successful exploit of this vulnerability may lead to information disclosure.

Threat Intelligence Overview

EPSS Score
0.0%
Top 87% exploitable
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy