How many CVEs have patched get_block_instance?

2 published CVEs changed get_block_instance in gradio-app/gradio, in 3 distinct patches totalling 12 changed lines, between 2023 and 2026.

What is the latest CVE that changed get_block_instance?

CVE-2026-28416 (Gradio has SSRF via Malicious `proxy_url` Injection in `gr.load()` Config Processing), published 2026-02-27, changed lines 1235 to 1238 of gradio/blocks.py.

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

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

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

get_block_instance

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

gradio/blocks.py

Last patched February 27, 2026

2

CVEs

That changed this function

3

Distinct patches

Backports counted once

12

Lines changed

Added plus removed

2023–2026

Years

By CVE publication date

Overview

get_block_instance in gradio-app/gradio was changed by 2 published CVE fixes between 2023 and 2026, in 3 distinct patches that added or removed 12 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 get_block_instance, newest first, with the lines each fix touched.

Gradio has SSRF via Malicious `proxy_url` Injection in `gr.load()` Config Processing
CVE-2026-28416 · lines 1235–1238 · +4 −1
High · CVSS 8.6
EPSS 0.3%2026-02-27
Gradio vulnerable to arbitrary file read and proxying of arbitrary URLs
CVE-2023-34239 · lines 789–795 · +6 −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 reverse_proxy2 CVEs · gradio/routes.py

All patched functions in gradio-app/gradio

Frequently asked questions

Common questions about CVE fixes to get_block_instance.

How many CVEs have patched get_block_instance?: 2 published CVEs changed get_block_instance in gradio-app/gradio, in 3 distinct patches totalling 12 changed lines, between 2023 and 2026.
What is the latest CVE that changed get_block_instance?: CVE-2026-28416 (Gradio has SSRF via Malicious `proxy_url` Injection in `gr.load()` Config Processing), published 2026-02-27, changed lines 1235 to 1238 of gradio/blocks.py.
How does get_block_instance compare to the rest of gradio-app/gradio?: gradio-app/gradio has 24 CVEs with a located fix in total; 2 of them changed get_block_instance.
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