How many CVEs have patched is_allowed_file?

1 published CVEs changed is_allowed_file in gradio-app/gradio, in 1 distinct patches totalling 3 changed lines, between 2025 and 2025.

What is the latest CVE that changed is_allowed_file?

CVE-2025-23042 (Gradio Blocked Path ACL Bypass Vulnerability), published 2025-01-14, changed lines 1516 to 1517 of gradio/utils.py.

How does is_allowed_file compare to the rest of gradio-app/gradio?

gradio-app/gradio has 24 CVEs with a located fix in total; 1 of them changed is_allowed_file.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

gradio-app/gradio

Function

is_allowed_file

Name: is_allowed_file in gradio-app/gradio: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

gradio/utils.py

Last patched January 14, 2025

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

3

Lines changed

Added plus removed

2025

Years

By CVE publication date

Overview

is_allowed_file in gradio-app/gradio was changed by 1 published CVE fixes in 2025, in 1 distinct patches that added or removed 3 lines in total.

gradio-app/gradio has 24 CVEs with a located fix in total, so 4% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed is_allowed_file, newest first, with the lines each fix touched.

Gradio Blocked Path ACL Bypass Vulnerability
CVE-2025-23042 · lines 1516–1517 · +2 −1
Critical · CVSS 9.1
EPSS 1.0%2025-01-14

Get an alert when the next CVE fix lands in gradio-app/gradio, with the patched functions.

Monitor gradio CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in gradio-app/gradio changed by the most CVE fixes.

file5 CVEs · gradio/routes.py build_proxy_request3 CVEs · gradio/routes.py is_in_or_equal3 CVEs · gradio/utils.py __init__3 CVEs · gradio/blocks.py _move_to_cache3 CVEs · gradio/processing_utils.py reverse_proxy2 CVEs · gradio/routes.py

All patched functions in gradio-app/gradio

Frequently asked questions

Common questions about CVE fixes to is_allowed_file.

How many CVEs have patched is_allowed_file?: 1 published CVEs changed is_allowed_file in gradio-app/gradio, in 1 distinct patches totalling 3 changed lines, between 2025 and 2025.
What is the latest CVE that changed is_allowed_file?: CVE-2025-23042 (Gradio Blocked Path ACL Bypass Vulnerability), published 2025-01-14, changed lines 1516 to 1517 of gradio/utils.py.
How does is_allowed_file compare to the rest of gradio-app/gradio?: gradio-app/gradio has 24 CVEs with a located fix in total; 1 of them changed is_allowed_file.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track gradio-app/gradio CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing