Gradio has an Open Redirect in its OAuth Flow

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

EPSS

• CVE-2026-28415: 0.29% estimated exploitation activity in the next 30 days; percentile 21.44 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The redirecttotarget() function in Gradio's OAuth flow accepts an unvalidated targeturl query parameter, allowing redirection to arbitrary external URLs. This affects the /logout and /login/callback endpoints on Gradio apps with OAuth enabled (i.e. apps running on Hugging Face Spaces with gr.LoginButton). Details An attacker can craft a URL like https://my-space.hf.space/logout?targeturl=https://evil.com/phishing that redirects the user to an external site after logout. Because the URL originates from a trusted hf.space domain, users are more likely to trust the link. Impact Phishing — an attacker can use the trusted domain to redirect users to a malicious site. No direct data exposure or server-side impact.

Fix The targeturl parameter is now sanitized to only use the path, query, and fragment, stripping any scheme or host.

Published by the source

1 Mar 2026, 01:29 UTC

Last modified by the source

6 Jun 2026, 00:30 UTC

Source last checked

26 Oct 2026, 13:42 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-pfjf-5gxr-995x

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-pfjf-5gxr-995x

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-28415

Advisory: Gradio has an Open Redirect in its OAuth Flow
IDs: CVE-2026-28415, GHSA-pfjf-5gxr-995x
Record: https://patchnext.com/advisories/cve-2026-28415 (revision 2, source checked 26 Oct 2026, 13:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gradio 6.6.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI gradio: affected < 6.6.0; fixed in 6.6.0

## Suggested inspection (read-only)
- `python -m pip show gradio`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on gradio.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-pfjf-5gxr-995x (OSV record GHSA-pfjf-5gxr-995x lists affected ranges: PyPI gradio >=0 <6.6.0 (fixed))
- Verified: https://github.com/advisories/GHSA-pfjf-5gxr-995x (GitHub-reviewed advisory GHSA-pfjf-5gxr-995x lists affected ranges: PyPI gradio >=0 <6.6.0)

Commands are suggestions: review each one before running it.