How many CVEs have patched reverse_proxy?

2 published CVEs changed reverse_proxy in gradio-app/gradio, in 4 distinct patches totalling 16 changed lines, between 2023 and 2026.

What is the latest CVE that changed reverse_proxy?

CVE-2026-48545 (Gradio < 6.15.0 Cookie Injection via Shared Proxy Client), published 2026-05-27, changed lines 1187 to 1197 of gradio/routes.py.

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

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

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

reverse_proxy

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

gradio/routes.py

Last patched May 27, 2026

2

CVEs

That changed this function

4

Distinct patches

Backports counted once

16

Lines changed

Added plus removed

2023–2026

Years

By CVE publication date

Overview

reverse_proxy in gradio-app/gradio was changed by 2 published CVE fixes between 2023 and 2026, in 4 distinct patches that added or removed 16 lines in total.

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

CVEs that patched it

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

Gradio < 6.15.0 Cookie Injection via Shared Proxy Client
CVE-2026-48545 · lines 1187–1197 · +9 −2
High · CVSS 7.6
EPSS 0.5%2026-05-27
Gradio vulnerable to arbitrary file read and proxying of arbitrary URLs
CVE-2023-34239 · lines 321–324 · +4 −1
Medium · CVSS 6.9
EPSS 0.7%2023-06-07

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 get_block_instance2 CVEs · gradio/blocks.py

All patched functions in gradio-app/gradio

Frequently asked questions

Common questions about CVE fixes to reverse_proxy.

How many CVEs have patched reverse_proxy?: 2 published CVEs changed reverse_proxy in gradio-app/gradio, in 4 distinct patches totalling 16 changed lines, between 2023 and 2026.
What is the latest CVE that changed reverse_proxy?: CVE-2026-48545 (Gradio < 6.15.0 Cookie Injection via Shared Proxy Client), published 2026-05-27, changed lines 1187 to 1197 of gradio/routes.py.
How does reverse_proxy compare to the rest of gradio-app/gradio?: gradio-app/gradio has 24 CVEs with a located fix in total; 2 of them changed reverse_proxy.
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