Advisory record · GHSA-r364-m2j9-mf4h

gradio Server-Side Request Forgery vulnerability

CVSS 7.3 HighEPSS 0.0042 · 36th percentile

Published by the GitHub Advisory Database at 27 Mar 2024, 03:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
gradioPyPI<4.18.04.18.0
Identifiers
GHSA-r364-m2j9-mf4h · CVE-2024-2206 · PYSEC-2026-1420
Weakness (CWE)
CWE-918
Published
27 Mar 2024
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Gradio versions before 4.18.0 are vulnerable to server-side request forgery through the /proxy route. An attacker who can send requests to the server can add arbitrary URLs for proxying by manipulating a header on requests to the / and /config routes, which can allow access to internal endpoints. Upgrade gradio to version 4.18.0 or later.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.3 High 3.0 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L CNA (@huntr_ai)
  • CISA KEV Not listed.
  • EPSS 0.0042, the 36th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:35 UTC First seen by agentprime
  2. 31 Oct 2026, 14:35 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.