Medium

Gradio's CORS origin validation accepts the null origin

  • Disclosed: 10.10.2024
  • Updated: 11.10.2026 12:19

Impact

What kind of vulnerability is it? Who is impacted?

This vulnerability relates to CORS origin validation accepting a null origin. When a Gradio server is deployed locally, the localhost_aliases variable includes "null" as a valid origin. This allows attackers to make unauthorized requests from sandboxed iframes or other sources with a null origin, potentially leading to data theft, such as user authentication tokens or uploaded files. This impacts users running Gradio locally, especially those using basic authentication.

Patches

Yes, please upgrade to gradio>=5.0 to address this issue.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

As a workaround, users can manually modify the localhost_aliases list in their local Gradio deployment to exclude "null" as a valid origin. By removing this value, the Gradio server will no longer accept requests from sandboxed iframes or sources with a null origin, mitigating the potential for exploitation.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) gradio < 5.0.0 5.0.0

References

CVSS score 5.4/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
Weakness (CWE)
CWE-285, CWE-346
Platform
Python (PyPI)
Package
gradio
Disclosed
10.10.2024
Updated
11.10.2026 12:19

Sources and licenses

OSV / GitHub Advisory Database - PYSEC-2024-214 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - GHSA-89v2-pqfv-c5r9 - CC BY 4.0

Vulnerability history: gradio

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (51) in the archive
Total entries
51
First → latest
12.2021 07.2026
Without a fix
13
Exploited in attacks
0

Severity breakdown

  • Critical 5
  • High 19
  • Medium 22
  • Low 5

Disclosures per year

  1. 2021: 1
  2. 2022: 1
  3. 2023: 5
  4. 2024: 28
  5. 2025: 9
  6. 2026: 7
Severity:
  1. High · 7.5 CVE-2024-8966 <= 5.22.0 no fix
  2. High · 7.5 CVE-2024-10624 >= 4.38.0, <= 5.0.0-beta.2 no fix
  3. High · 8.2 CVE-2024-10648 >= 4.0.0, <= 5.0.0b2 no fix
  4. High · 7.5 CVE-2024-10569 >= 4.0.0, <= 5.0.0b2 no fix
  5. Critical CVE-2025-23042 < 5.11.0 5.11.0
  6. High · 7.5 CVE-2024-47867 < 5.0.0 5.0.0
  7. Gradio's CORS origin validation accepts the null origin this entry
    Medium · 5.4 CVE-2024-47165 < 5.0.0 5.0.0
  8. High · 8.1 CVE-2024-1728 < 4.19.2 4.19.2
  9. High · 8.6 CVE-2024-4325 <= 4.36.0 no fix
  10. High · 7.5 CVE-2024-34510 < 4.20.0 4.20.0
  11. High · 7.5 CVE-2024-1561 < 4.13.0 4.13.0
  12. High · 7.3 CVE-2024-2206 < 4.18.0 4.18.0
  13. Critical · 8.3 CVE-2021-43831 < 2.5.0 2.5.0

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.