Medium

Gradio performs a non-constant-time comparison when comparing hashes

  • Disclosed: 10.10.2024
  • Updated: 11.10.2026 12:19

Impact

What kind of vulnerability is it? Who is impacted?

This vulnerability involves a timing attack in the way Gradio compares hashes for the analytics_dashboard function. Since the comparison is not done in constant time, an attacker could exploit this by measuring the response time of different requests to infer the correct hash byte-by-byte. This can lead to unauthorized access to the analytics dashboard, especially if the attacker can repeatedly query the system with different keys.

Patches

Yes, please upgrade to gradio>4.44 to mitigate this issue.

Workarounds

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

To mitigate the risk before applying the patch, developers can manually patch the analytics_dashboard dashboard to use a constant-time comparison function for comparing sensitive values, such as hashes. Alternatively, access to the analytics dashboard can be disabled.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) gradio < 4.44.0 4.44.0

References

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

Sources and licenses

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

OSV / GitHub Advisory Database - GHSA-j757-pf57-f8r4 - 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 performs a non-constant-time comparison when comparing hashes this entry
    Medium · 3.7 CVE-2024-47869 < 4.44.0 4.44.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
Show more (5) Showing 20 of 25

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.