LiveActive security incident?Get immediate response
CVE Record

CVE-2026-28416: Gradio has SSRF via Malicious `proxy_url` Injection in `gr.load()` Config Processing

Gradio is an open-source Python package designed for quick prototyping. Prior to version 6.6.0, a Server-Side Request Forgery (SSRF) vulnerability in Gradio allows an attacker to make arbitrary HTTP requests from a victim's server by hosting a malicious Gradio Space. When a victim application uses `gr.load()` to load an attacker-controlled Space, the malicious `proxy_url` from the config is trusted and added to the allowlist, enabling the attacker to access internal services, cloud metadata endpoints, and private networks through the victim's infrastructure. Version 6.6.0 fixes the issue.

HighCVSS 8.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-28416 is a high-severity SSRF issue in Gradio before 6.6.0. If an application uses `gr.load()` to load an attacker-controlled Gradio Space, the attacker can cause the server to make unintended HTTP requests, potentially reaching internal services or cloud metadata from the victim environment.

Executive priority

Treat this as a prompt upgrade for affected Gradio deployments, especially internet-facing AI apps or systems in cloud environments. The main business risk is unintended access to internal endpoints through trusted server infrastructure.

Technical view

Gradio trusted a `proxy_url` value from a loaded Space configuration and added it to an allowlist during `gr.load()` processing. This allowed arbitrary server-side HTTP requests from the victim server context. The issue is categorized as CWE-918 and is fixed in Gradio 6.6.0.

Likely exposure

Exposure is most likely in Python applications using Gradio versions earlier than 6.6.0 and calling `gr.load()` on Spaces or sources not fully controlled by the application owner.

Exploitation context

The provided sources describe remote, unauthenticated SSRF with low complexity and no user interaction in CVSS terms. They do not state active exploitation, and the CVE is not marked as KEV in the supplied data.

Researcher notes

Evidence is limited to the CVE record and GitHub advisory. The key validation point is whether vulnerable versions use `gr.load()` with attacker-controlled Spaces. No public exploit status or additional affected products are provided in the source bundle.

Mitigation direction

  • Upgrade Gradio to version 6.6.0 or later.
  • Avoid loading untrusted or attacker-controlled Spaces with `gr.load()`.
  • Review vendor advisory for any updated remediation guidance.
  • Restrict server egress to internal services and metadata endpoints where feasible.

Validation and detection

  • Inventory applications and containers using the Gradio Python package.
  • Confirm installed Gradio versions are 6.6.0 or later.
  • Search code for `gr.load()` usage.
  • Identify whether loaded Spaces are externally controlled or user-supplied.
  • Review egress controls protecting internal services and cloud metadata endpoints.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-918: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-28416 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N3.94.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.2High
CVSS 3.1 vector shape for CVE-2026-28416Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
gradio-appgradio< 6.6.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-918 · source CWE mapping

CWE mapping pending import

This CVE carries a CWE mapping that will resolve to a full Glexia CWE intelligence page after the official CWE import is complete.