Products / gradio
gradio
50 records.
- Gradio FileExplorer preprocess path traversal allows files outside root_dir to reach callbacks
- Gradio: Audio cache key ignores metadata when saving numpy audio outputs Gradio builds the audio cache key with a weak hash that ignores metadata, so colliding inputs can receive each other's cached audio.
- Gradio contains a cookie injection vulnerability A proxy's shared HTTP client stores and replays a parent-domain cookie set by an attacker's Space into other users' requests.
- Gradio is Vulnerable to Absolute Path Traversal on Windows with Python 3.13+ On Windows with Python 3.13 or later, root-relative paths pass Gradio's safe-join check, letting unauthenticated requests read arbitrary files.
- Gradio: Mocked OAuth Login Exposes Server Credentials and Uses Hardcoded Session Secret
- Gradio has SSRF via Malicious `proxy_url` Injection in `gr.load()` Config Processing
- Gradio has an Open Redirect in its OAuth Flow
- Gradio Allows Unauthorized File Copy via Path Manipulation The flagging feature copies any server file named in an unauthenticated predict request, without validating the supplied path first.
- Gradio CORS Origin Validation Bypass Vulnerability
- Gradio DOS in multipart boundry while uploading the file
- Gradio Vulnerable to Open Redirect A URL-encoded crafted request makes the server return a 302 redirect to an attacker-chosen external site.
- Gradio Vulnerable to Denial of Service (DoS) via Crafted Zip Bomb An uploaded compressed archive expands to a huge size when the dataframe component parses it with pandas, exhausting resources and crashing the server.
- Gradio Vulnerable to Arbitrary File Deletion
- Gradio Path Traversal vulnerability
- Gradio Vulnerable to Denial of Service (DoS) via Crafted HTTP Request
- Gradio Blocked Path ACL Bypass Vulnerability
- Gradio vulnerable to arbitrary file read with File and UploadButton components
- gradio Server Side Request Forgery vulnerability The save_url_to_cache function fetches any supplied URL without restriction, letting an attacker make the server download local or internal resources.
- Gradio's dropdown component pre-process step does not limit the values to those in the dropdown list Crafted requests can send values outside the dropdown's configured list, ignoring the allow_custom_value restriction on the server side.
- Gradio uses insecure communication between the FRP client and server The tunnel used by share=True runs without enforced HTTPS, so an on-path observer can read uploaded files and modify traffic.
- Gradio has a one-level read path traversal in `/custom_component` A path parameter on the custom component endpoint can climb one directory level, letting remote requests read source files of custom components.
- Gradios's CORS origin validation is not performed when the request has a cookie Gradio skips CORS origin validation for requests carrying cookies, so a malicious site can make authenticated cross-origin requests to a local server.
- Gradio has several components with post-process steps allow arbitrary file leaks Gradio file components accept arbitrary file paths from requests that bypass intended input constraints, so the server returns sensitive local files.
- Gradio vulnerable to SSRF in the path parameter of /queue/join The queue join endpoint makes the server fetch attacker-supplied URLs and cache the results, reaching internal hosts.
- Gradio's `is_in_or_equal` function may be bypassed Path checks that rely on parent-directory sequences fail to normalise certain inputs, letting requests reach files outside the permitted directory.
- Gradio's CORS origin validation accepts the null origin The localhost origin list includes the null origin, so sandboxed iframes can make cross-origin requests and read the responses.
- Gradio lacks integrity checking on the downloaded FRP client The FRP client binary downloaded for sharing is used without verifying a checksum or signature, so a tampered download would be executed.
- Gradio has an XSS on every Gradio server via upload of HTML files, JS files, or SVG files
- In Gradio, the `enable_monitoring` flag set to `False` does not disable monitoring
- Gradio performs a non-constant-time comparison when comparing hashes
- Gradio has a race condition in update_root_in_config may redirect user traffic
- Gradio allows users to access arbitrary files
- Open redirect in gradio
- Local file inclusion in gradio Output parsed as JSON containing a path key makes the server copy that local file into the cache, where it can later be fetched.
- Server-Side Request Forgery in gradio Gradio's queue endpoint fetches attacker-supplied URLs server-side through a cache helper without validation, reaching internal hosts and cloud metadata services.
- Gradio applications running locally vulnerable to 3rd party websites accessing routes and uploading files A locally running Gradio server accepts requests from arbitrary websites, so a visited page can upload files to the user's machine.
- Gradio's Component Server does not properly consider` _is_server_fn` for functions The Component Server does not check the server-function flag on functions, so non-server functions can be invoked.
- Gradio allows credential leakage on Windows
- gradio vulnerable to Path Traversal
- gradio Server-Side Request Forgery vulnerability
- gradio Server-Side Request Forgery vulnerability
- Gradio apps vulnerable to timing attacks to guess password
- Gradio Path Traversal vulnerability A crafted JSON value in a Gradio API request makes the server include and read an arbitrary local file.
- Gradio makes the `/file` secure against file traversal and server-side request forgery attacks Raw HTTP tools could read arbitrary server files and make server-side requests through Gradio's file route, which browser-style URLs could not reach.
- Gradio Exposure of Sensitive Information to an Unauthorized Actor vulnerability
- Gradio arbitrary file upload vulnerability
- Gradio vulnerable to arbitrary file read and proxying of arbitrary URLs Shared Gradio apps let remote users read arbitrary files on the host and use the host to proxy requests to arbitrary URLs.
- Update share links to use FRP instead of SSH tunneling The share link tunnel sends a private SSH key to connecting clients, which lets them reach other users' shared demos.
- Improper Neutralization of Formula Elements in a CSV File in Gradio Flagging
- Files on the host computer can be accessed from the Gradio interface