CVE-2024-47871

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.2% (7th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.1 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2024-10-10) is not newer than that change (2024-10-17), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2024-0074 (ENISA EUVD) · GHSA-279j-x4gx-hfrh (GitHub Security Advisories) · PYSEC-2024-219 (OSV.dev)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Gradio is an open-source Python package designed for quick prototyping. This vulnerability involves insecure communication between the FRP (Fast Reverse Proxy) client and server when Gradio's share=True option is used. HTTPS is not enforced on the connection, allowing attackers to intercept and read files uploaded to the Gradio server, as well as modify responses or data sent between the client and server. This impacts users who are sharing Gradio demos publicly over the internet using share=True without proper encryption, exposing sensitive data to potential eavesdroppers. Users are advised to upgrade to gradio>=5 to address this issue. As a workaround, users can avoid using share=True in production environments and instead host their Gradio applications on servers with HTTPS enabled to ensure secure communication.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
7th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 10, 2024

Last Modified

October 17, 2024

Advisory Details (1)

Auto-updated Jul 23, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Insecure communication between the FRP client and server · Advisory · gradio-app/gradio · GitHub

https://github.com/gradio-app/gradio/security/advisories/GHSA-279j-x4gx-hfrh

Vendor Advisories for CVE-2024-47871(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipgradio @ 5.0.0 (fixes < 5.0.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
gradio0.1.0 ... 5.0.0b9 (554 versions)
  • every version up to 5.0.0: fixed in 5.0.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 42× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 265 rows on record for this CVE, as 99 entries (1 repeat merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 165 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 01:08 UTCEchelonGraph re-scored
  2. 2026-11-13 01:08 UTCGHSA enrichmentGHSA-279j-x4gx-hfrh · GitHub severity HIGH · GitHub CVSS 8.1
  3. 2026-11-12 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  4. 2026-11-12 01:58 UTCEchelonGraph re-scored
  5. 2026-11-12 01:58 UTCGHSA enrichmentGHSA-279j-x4gx-hfrh · GitHub severity HIGH · GitHub CVSS 8.1
  6. 2026-11-11 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  7. 2026-11-11 02:51 UTCEchelonGraph re-scored
  8. 2026-11-11 02:51 UTCGHSA enrichmentGHSA-279j-x4gx-hfrh · GitHub severity HIGH · GitHub CVSS 8.1
  9. 2026-11-10 16:39 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-11-10 03:31 UTCEchelonGraph re-scored
  11. 2026-11-10 03:31 UTCGHSA enrichmentGHSA-279j-x4gx-hfrh · GitHub severity HIGH · GitHub CVSS 8.1
  12. 2026-11-09 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  13. 2026-11-09 04:25 UTCEchelonGraph re-scored
  14. 2026-11-09 04:25 UTCGHSA enrichmentGHSA-279j-x4gx-hfrh · GitHub severity HIGH · GitHub CVSS 8.1
  15. 2026-11-08 16:36 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  16. 2026-11-08 05:15 UTCEchelonGraph re-scored
  17. 2026-11-08 05:15 UTCGHSA enrichmentGHSA-279j-x4gx-hfrh · GitHub severity HIGH · GitHub CVSS 8.1
  18. 2026-11-07 16:36 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-11-07 06:08 UTCEchelonGraph re-scored
  20. 2026-11-07 06:08 UTCGHSA enrichmentGHSA-279j-x4gx-hfrh · GitHub severity HIGH · GitHub CVSS 8.1
  21. 2026-11-06 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  22. 2026-11-06 06:59 UTCEchelonGraph re-scored
  23. 2026-11-06 06:59 UTCGHSA enrichmentGHSA-279j-x4gx-hfrh · GitHub severity HIGH · GitHub CVSS 8.1
  24. 2026-11-05 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  25. 2026-11-05 07:52 UTCEchelonGraph re-scored
Show 74 more
  1. 2026-11-05 07:52 UTCGHSA enrichmentGHSA-279j-x4gx-hfrh · GitHub severity HIGH · GitHub CVSS 8.1
  2. 2026-11-05 03:25 UTCOSV refresh
  3. 2026-11-04 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  4. 2026-11-04 08:45 UTCEchelonGraph re-scored
  5. 2026-11-04 08:45 UTCGHSA enrichmentGHSA-279j-x4gx-hfrh · GitHub severity HIGH · GitHub CVSS 8.1
  6. 2026-11-03 16:43 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  7. 2026-11-03 09:38 UTCEchelonGraph re-scored
  8. 2026-11-03 09:38 UTCGHSA enrichmentGHSA-279j-x4gx-hfrh · GitHub severity HIGH · GitHub CVSS 8.1
  9. 2026-11-02 16:41 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-11-02 10:31 UTCEchelonGraph re-scored
  11. 2026-11-02 10:31 UTCGHSA enrichmentGHSA-279j-x4gx-hfrh · GitHub severity HIGH · GitHub CVSS 8.1
  12. 2026-11-01 11:24 UTCGHSA enrichmentGHSA-279j-x4gx-hfrh · GitHub severity HIGH · GitHub CVSS 8.1
  13. 2026-11-01 08:11 UTCGHSA enrichmentGHSA-279j-x4gx-hfrh · GitHub severity HIGH · GitHub CVSS 8.1
  14. 2026-11-01 08:11 UTCEchelonGraph re-scored
  15. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  16. 2026-10-31 12:18 UTCEchelonGraph re-scored
  17. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-10-30 13:11 UTCEchelonGraph re-scored
  19. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  20. 2026-10-29 14:04 UTCEchelonGraph re-scored
  21. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  22. 2026-10-28 14:57 UTCEchelonGraph re-scored
  23. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  24. 2026-10-27 15:34 UTCEchelonGraph re-scored
  25. 2026-10-25 17:00 UTCEchelonGraph re-scored
  26. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  27. 2026-10-24 17:54 UTCEchelonGraph re-scored
  28. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  29. 2026-10-23 18:47 UTCEchelonGraph re-scored
  30. 2026-10-22 19:36 UTCEchelonGraph re-scored
  31. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  32. 2026-10-21 20:29 UTCEchelonGraph re-scored
  33. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  34. 2026-10-20 21:23 UTCEchelonGraph re-scored
  35. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  36. 2026-10-19 22:12 UTCEchelonGraph re-scored
  37. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  38. 2026-10-18 20:59 UTCEchelonGraph re-scored
  39. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  40. 2026-10-18 06:57 UTCEchelonGraph re-scored
  41. 2026-10-17 21:31 UTCEchelonGraph re-scored
  42. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  43. 2026-10-16 22:23 UTCEchelonGraph re-scored
  44. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  45. 2026-10-15 19:03 UTCEchelonGraph re-scored
  46. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  47. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  48. 2026-10-14 12:48 UTCEchelonGraph re-scored
  49. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  50. 2026-10-12 17:43 UTCEchelonGraph re-scored
  51. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  52. 2026-10-11 21:08 UTCEchelonGraph re-scored
  53. 2026-10-11 16:01 UTCEchelonGraph re-scored
  54. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  55. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  56. 2026-10-10 11:55 UTCOSV refresh
  57. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  58. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  59. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  60. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  61. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  62. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  63. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  64. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  65. 2026-09-30 19:55 UTCEchelonGraph re-scored
  66. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  67. 2026-09-29 15:18 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  68. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  69. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  70. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  71. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  72. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  73. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  74. 2026-09-20 21:53 UTCOSV refresh

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2024-47871?
CVE-2024-47871 is a critical-severity vulnerability; its CVE record was published on October 10, 2024. Gradio is an open-source Python package designed for quick prototyping. This vulnerability involves insecure communication between the FRP (Fast Reverse Proxy) client and server when Gradio's share=True option is used. HTTPS is not enforced on the connection, allowing attackers to intercept and…
When was the CVE record for CVE-2024-47871 published?
The CVE record for CVE-2024-47871 was published on October 10, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 17, 2024; the record at its source may have been updated since.
Is CVE-2024-47871 actively exploited?
CVE-2024-47871 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-47871?
CVE-2024-47871 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2024-47871?
A fix for CVE-2024-47871 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-47871 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-47871?

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

Book a Demo →Browse All CVEs