CVE-2024-1728

HIGHNVD 7.59.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 85% probability of exploitation within the next 30 days (top 0.3% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Weaponized
7.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 85%
CISA-KEV: Not listedEPSS: 85%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

gradio-app/gradio is vulnerable to a local file inclusion vulnerability due to improper validation of user-supplied input in the UploadButton component. Attackers can exploit this vulnerability to read arbitrary files on the filesystem, such as private SSH keys, by manipulating the file path in the request to the /queue/join endpoint. This issue could potentially lead to remote code execution. The vulnerability is present in the handling of file upload paths, allowing attackers to redirect file uploads to unintended locations on the server.

CVSS v3
7.5
EG Score
9.0(high)
EG Risk
90(Attend)
EG Risk 90/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation85% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
99.7%
KEV
Not listed

Published

April 10, 2024

Last Modified

July 30, 2025

References (4)

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
gradio0.1.0 ... 4.9.1 (508 versions)4.19.2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 02:32 UTCEG score recompute
  2. 2026-07-22 23:19 UTCEG score recompute
  3. 2026-07-22 14:07 UTCEPSS rescore
  4. 2026-07-20 17:06 UTCEPSS rescore
  5. 2026-07-15 16:56 UTCEPSS rescore
  6. 2026-07-15 16:56 UTCEPSS rescore
  7. 2026-07-15 01:59 UTCEPSS rescore
  8. 2026-07-15 01:59 UTCEPSS rescore
  9. 2026-07-14 14:25 UTCOSV refresh
  10. 2026-07-13 22:28 UTCEPSS rescore
  11. 2026-07-11 08:26 UTCEPSS rescore
  12. 2026-07-06 02:22 UTCEPSS rescore
  13. 2026-07-06 02:22 UTCEPSS rescore
  14. 2026-07-01 15:05 UTCEPSS rescore
  15. 2026-06-28 04:55 UTCEPSS rescore
  16. 2026-06-26 15:07 UTCOSV refresh
  17. 2026-06-25 13:48 UTCEPSS rescore
  18. 2026-06-23 21:32 UTCEPSS rescore
  19. 2026-06-23 21:31 UTCEPSS rescore
  20. 2026-06-17 17:52 UTCEPSS rescore
  21. 2026-06-17 17:51 UTCEPSS rescore
  22. 2026-06-15 17:47 UTCEPSS rescore
  23. 2026-06-13 22:59 UTCEPSS rescore
  24. 2026-06-13 22:59 UTCEPSS rescore
  25. 2026-06-12 23:11 UTCEPSS rescore
Show 25 more
  1. 2026-06-12 23:11 UTCEPSS rescore
  2. 2026-06-10 22:17 UTCEPSS rescore
  3. 2026-06-10 22:17 UTCEPSS rescore
  4. 2026-06-10 13:21 UTCEPSS rescore
  5. 2026-06-10 13:21 UTCEPSS rescore
  6. 2026-06-08 21:42 UTCOSV refresh
  7. 2026-06-08 14:16 UTCEPSS rescore
  8. 2026-06-08 14:16 UTCEPSS rescore
  9. 2026-06-07 15:24 UTCEPSS rescore
  10. 2026-06-07 15:24 UTCEPSS rescore
  11. 2026-06-06 13:46 UTCEPSS rescore
  12. 2026-06-06 13:46 UTCEPSS rescore
  13. 2026-06-05 22:46 UTCEPSS rescore
  14. 2026-06-05 22:46 UTCEPSS rescore
  15. 2026-05-31 22:30 UTCEPSS rescore
  16. 2026-05-31 22:30 UTCEPSS rescore
  17. 2026-05-31 00:15 UTCEPSS rescore
  18. 2026-05-31 00:15 UTCEPSS rescore
  19. 2026-05-28 13:44 UTCEPSS rescore
  20. 2026-05-28 13:44 UTCEPSS rescore
  21. 2026-05-28 13:44 UTCEPSS rescore
  22. 2026-05-27 13:40 UTCEPSS rescore
  23. 2026-05-26 13:43 UTCEPSS rescore
  24. 2026-05-26 13:43 UTCEPSS rescore
  25. 2026-05-24 04:45 UTCEG score recompute

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2024/CVE-2024-1728.yaml
    First seen Jan 1, 2024

    Gradio > 4.19.1 UploadButton - Path Traversal

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-1728?
CVE-2024-1728 is a high vulnerability published on April 10, 2024. gradio-app/gradio is vulnerable to a local file inclusion vulnerability due to improper validation of user-supplied input in the UploadButton component. Attackers can exploit this vulnerability to read arbitrary files on the filesystem, such as private SSH keys, by manipulating the file path in the…
When was CVE-2024-1728 disclosed?
CVE-2024-1728 was first published in the National Vulnerability Database on April 10, 2024, with the most recent update on July 30, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-1728 actively exploited?
CVE-2024-1728 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-1728?
CVE-2024-1728 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2024-1728?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-1728, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-1728

Explore →

Is Your Infrastructure Affected by CVE-2024-1728?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs