CVE-2024-39602

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2025-01-14. NVD baseline CVSS 9.1; sources differ by 0.0.

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

Also known asEUVD-2024-38391 (ENISA EUVD) · GHSA-cv67-v84q-6c9x (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan mitigationNo fix is confirmed yet: check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2.4%CVSS: 9.1Exploit: None knownExposed services: Not assessed

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

An external config control vulnerability exists in the nas.cgi set_nas() functionality of Wavlink AC3000 M33A8.V5030.210505. A specially crafted HTTP request can lead to arbitrary command execution. An attacker can make an authenticated HTTP request to trigger this vulnerability.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
42
EG Risk 42/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.
Exploitation2.4% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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: No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule.
EPSS PROB
2.4%
EPSS %ILE
84th
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.GitHub Security Advisory CVSS
EG Likelihood
2.4% 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.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 low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

January 14, 2025

Last Modified

August 21, 2025

Advisory Details (2)

Auto-updated Aug 1, 2026
No fix on record yet.
Web page

TALOS-2024-2052 || Cisco Talos Intelligence Group - Comprehensive Threat Intelligence

https://www.talosintelligence.com/vulnerability_reports/TALOS-2024-2052
Web page

TALOS-2024-2052 || Cisco Talos Intelligence Group - Comprehensive Threat Intelligence

https://talosintelligence.com/vulnerability_reports/TALOS-2024-2052

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 60× 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 269 rows on record for this CVE.

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. None are among the latest 100 rows. The 169 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-39602?
CVE-2024-39602 is a critical-severity vulnerability; its CVE record was published on January 14, 2025. An external config control vulnerability exists in the nas.cgi set_nas() functionality of Wavlink AC3000 M33A8.V5030.210505. A specially crafted HTTP request can lead to arbitrary command execution. An attacker can make an authenticated HTTP request to trigger this vulnerability.
When was the CVE record for CVE-2024-39602 published?
The CVE record for CVE-2024-39602 was published on January 14, 2025. 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 August 21, 2025; the record at its source may have been updated since.
Is CVE-2024-39602 actively exploited?
CVE-2024-39602 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.4% probability of exploitation in the next 30 days (84th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-39602?
CVE-2024-39602 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2024-39602?
No fix for CVE-2024-39602 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-39602

Explore →

Is Your Infrastructure Affected by CVE-2024-39602?

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