CVE-2026-49119 in Gradio
Gradio before 6.16.0 contain a path traversal vulnerability in the FileExplorer component's preprocess() method that allows unauthenticated attackers to escape the configured root directory by supplying path segments containing directory traversal sequences or absolute paths. Attackers can provide crafted path segments that cause os.path.join to discard the root_dir prefix entirely, resulting in arbitrary file read or exposure of sensitive files outside the intended directory.
Quick answer
Gradio Project Gradio should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Gradio before 6.16.0
Fixed versions
- Gradio 6.16.0 or later
How to fix it
CVE-2026-49119 affects Gradio. In simple terms, private data may be shown to someone who should not see it. Update to Gradio 6.16.0 or later. If you cannot update today, limit who can reach this system until the fix is done.
- Find every place where Gradio is installed or used.
- Check if the version matches: Gradio before 6.16.0.
- Update to: Gradio 6.16.0 or later.
- If you cannot update now, allow only trusted users and trusted networks.
- Check logs for crashes, strange requests, failed logins, or unexpected access.
- Change secrets or passwords if you think data may have been exposed.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the installed version is now: Gradio 6.16.0 or later.
- Confirm the risky feature is no longer exposed to untrusted users.
- Run the affected workflow again and make sure it still works.
- Review logs again after the update.
- Run a new Fixnx scan if this software is part of a public website.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-49119?
Gradio Project Gradio versions listed as affected should be reviewed: Gradio before 6.16.0.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.