Quick answers
- Is CVE-2026-49119 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49119 being exploited in the wild.
- How severe is CVE-2026-49119?
- High severity, with a CVSS score of 7.5, published 1 July 2026.
- Which products and versions are affected?
- gradio (PyPI) < 6.16.0, ECOSYSTEM:introduced=0,fixed=6.16.0.
- Is there a fix for CVE-2026-49119?
- Yes. gradio (PyPI): upgrade to 6.16.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-49119 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-49119?
- Check whether you run gradio (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- gradio (PyPI): upgrade to 6.16.0 or later
pip install "gradio>=6.16.0"
Technical details
A path traversal vulnerability (CWE-22) exists in Gradio's FileExplorer component due to insecure path handling in the preprocess() method. The component used os.path.join() and os.path.normpath() on user-supplied path segments without sufficient validation. Because os.path.join() discards previous path components if an absolute path is encountered, and directory traversal sequences (../) were not filtered, an unauthenticated remote attacker could supply crafted inputs to escape the 'root_dir' restriction. This allows for arbitrary file read on the host system. The issue was resolved in version 6.16.0 by routing path processing through the _safe_join helper, which correctly validates that resolved paths remain within the intended directory.
Affected products
- gradio-app gradio < 6.16.0
Identifiers
- CVE-2026-49119
- GHSA-j36p-7w88-g82j
- PYSEC-2026-2179
Timeline
- 2026-05-29: patched: Fix PR submitted to gradio-app/gradio repository
- 2026-06-03: advisory: Release 6.16.0 published with security fix
- 2026-07-01: disclosed: CVE-2026-49119 published to NVD