CVE-2024-27102

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2024-03-15. NVD baseline CVSS 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2024-0814 (ENISA EUVD) · GHSA-494h-9924-xww9 (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Wings is the server control plane for Pterodactyl Panel. This vulnerability impacts anyone running the affected versions of Wings. The vulnerability can potentially be used to access files and directories on the host system. The full scope of impact is exactly unknown, but reading files outside of a server's base directory (sandbox root) is possible. In order to use this exploit, an attacker must have an existing "server" allocated and controlled by Wings. Details on the exploitation of this vulnerability are embargoed until March 27th, 2024 at 18:00 UTC. In order to mitigate this vulnerability, a full rewrite of the entire server filesystem was necessary. Because of this, the size of the patch is massive, however effort was made to reduce the amount of breaking changes. Users are advised to update to version 1.11.9. There are no known workarounds for this vulnerability.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
61
EG Risk 61/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
45th
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.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 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 low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (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.

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

March 13, 2024

Last Modified

January 23, 2025

Advisory Details (2)

Auto-updated Oct 27, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Symlink Race in Server Filesystem · Advisory · pterodactyl/wings · GitHub

https://github.com/pterodactyl/wings/security/advisories/GHSA-494h-9924-xww9
GitHub commit Patch Available

commit d1c0ca526007 (pterodactyl/wings)

Patch available: pterodactyl/wings v1.11.9 (contains commit d1c0ca526007)

https://github.com/pterodactyl/wings/commit/d1c0ca526007113a0f74f56eba99511b4e989287

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/pterodactyl/wings @ 1.11.9 (fixes < 1.11.9)—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)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/pterodactyl/wings—
  • every version up to 1.11.9: fixed in 1.11.9
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 55× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 98 of 227 refreshes 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 129 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2024-27102?
CVE-2024-27102 is a critical-severity vulnerability; its CVE record was published on March 13, 2024. Wings is the server control plane for Pterodactyl Panel. This vulnerability impacts anyone running the affected versions of Wings. The vulnerability can potentially be used to access files and directories on the host system. The full scope of impact is exactly unknown, but reading files outside of…
When was the CVE record for CVE-2024-27102 published?
The CVE record for CVE-2024-27102 was published on March 13, 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 January 23, 2025; the record at its source may have been updated since.
Is CVE-2024-27102 actively exploited?
CVE-2024-27102 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-27102?
CVE-2024-27102 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2024-27102?
A fix for CVE-2024-27102 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-27102?

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

Book a Demo →Browse All CVEs