Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-49119 – Arbitrary File Read / Path Traversal – Gradio before 6.16.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-49119 is a high-severity path traversal vulnerability in Gradio’s FileExplorer component, affecting all versions prior to 6.16.0. By supplying crafted path segments — including directory traversal sequences (../) or absolute paths — unauthenticated remote attackers can cause Python’s os.path.join to discard the configured root_dir prefix entirely, enabling arbitrary file reads from the server’s filesystem. The CVSS 4.0 score is 8.7 (HIGH).

Technical details

  • Root cause: The preprocess() method of Gradio’s gr.FileExplorer component fails to validate user-supplied file paths before passing them to os.path.join. When an absolute path or a path containing .. sequences is provided, os.path.join silently discards the root_dir prefix, resolving to a location entirely outside the intended directory boundary (CWE-22).
  • Trigger conditions: No authentication, no user interaction, and no special configuration are required. Any unauthenticated HTTP request to a Gradio application using the FileExplorer component can trigger the flaw.
  • Attack vector: Network-accessible; exploitable over the internet against any publicly reachable Gradio endpoint.
  • Impact: Arbitrary file read — an attacker can access any file readable by the server process, including environment variable files (e.g., /proc/self/environ), application secrets, API keys, cloud credentials, SSH keys, and model configuration files.

Affected software

  • Gradio — all versions prior to 6.16.0

Severity

CVSS v3.1 Base Score: 7.5 (HIGH)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Upgrade Gradio to version 6.16.0 or later. The fix introduces path validation via _safe_join in gr.FileExplorer.preprocess, which rejects absolute paths and any path segments containing .. that would escape the configured root_dir.
  • If immediate patching is not feasible: Restrict network access to Gradio instances at the firewall or reverse-proxy level. Ensure Gradio endpoints are not publicly reachable until patched. Additionally, audit the filesystem permissions of the account running the Gradio server to limit the scope of any potential file disclosure.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge