CVE-2024-25124

CRITICALNVD 9.49.4
EchelonGraph scoreMEDIUM confidence

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

Score 9.4 from GitHub Security Advisory (severity: CRITICAL) published 2024-02-22. NVD baseline CVSS 9.4; sources differ by 0.0.

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

Also known asEUVD-2024-0629 (ENISA EUVD) · GHSA-fmg4-x8pw-hjhg (GitHub Security Advisories) · GO-2024-2574 (OSV.dev)Source: ENISA EUVD

9.4EG
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.7%CVSS: 9.4Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Fiber is a web framework written in go. Prior to version 2.52.1, the CORS middleware allows for insecure configurations that could potentially expose the application to multiple CORS-related vulnerabilities. Specifically, it allows setting the Access-Control-Allow-Origin header to a wildcard (*) while also having the Access-Control-Allow-Credentials set to true, which goes against recommended security best practices. The impact of this misconfiguration is high as it can lead to unauthorized access to sensitive user data and expose the system to various types of attacks listed in the PortSwigger article linked in the references. Version 2.52.1 contains a patch for this issue. As a workaround, users may manually validate the CORS configurations in their implementation to ensure that they do not allow a wildcard origin when credentials are enabled. The browser fetch api, as well as browsers and utilities that enforce CORS policies, are not affected by this.

CVSS v3
9.4
EG Score
9.4CRITICALmedium confidence
EG Risk
58
EG Risk 58/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)
Severity94% × 45%
Impact severity (EG Severity): CVSS 9.4 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.7%
EPSS %ILE
51st
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.4): severity, escalated by confirmed exploitation. This CVE's 9.4 is its impact severity (EG Severity), not escalated.

EG Severity
9.4 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% 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, 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

February 21, 2024

Last Modified

February 5, 2025

Advisory Details (7)

Auto-updated Oct 2, 2026
Patch available. Sources: github_commit, github_release, github.
Web page

CORS misconfiguration for credentials transfer — CodeQL query help documentation

https://codeql.github.com/codeql-query-help/javascript/js-cors-misconfiguration-for-credentials
Web page

Saturn Cloud | Saturn Cloud | The Control Plane for GPU Clouds

https://saturncloud.io/blog/cors-cannot-use-wildcard-in-accesscontrolalloworigin-when-credentials-flag-is-true
GitHub advisoryMentions a patch (unverified)

Insecure CORS Configuration Allowing Wildcard Origin with Credentials · Advisory · gofiber/fiber · GitHub

https://github.com/gofiber/fiber/security/advisories/GHSA-fmg4-x8pw-hjhg
GitHub release Patch Available

v2.52.1

Patch available: gofiber/fiber v2.52.1

https://github.com/gofiber/fiber/releases/tag/v2.52.1
GitHub commit Patch Available

commit f0cd3b44b086 (gofiber/fiber)

Patch available: gofiber/fiber v2.52.1 (contains commit f0cd3b44b086)

https://github.com/gofiber/fiber/commit/f0cd3b44b086544a37886232d0530601f2406c23
Web page

Fetch Standard

https://fetch.spec.whatwg.org/#cors-protocol-and-credentials
Web page

Reason: Credential is not supported if the CORS header 'Access-Control-Allow-Origin' is '*' - HTTP | MDN

https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSNotSupportingCredentials

Vendor Advisories for CVE-2024-25124(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
gogithub.com/gofiber/fiber/v2 @ 2.52.1 (fixes < 2.52.1)—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/gofiber/fiber/v2—
  • every version up to 2.52.1: fixed in 2.52.1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 43× 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 262 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 162 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2024-25124?
CVE-2024-25124 is a critical-severity vulnerability; its CVE record was published on February 21, 2024. Fiber is a web framework written in go. Prior to version 2.52.1, the CORS middleware allows for insecure configurations that could potentially expose the application to multiple CORS-related vulnerabilities. Specifically, it allows setting the Access-Control-Allow-Origin header to a wildcard (*)…
When was the CVE record for CVE-2024-25124 published?
The CVE record for CVE-2024-25124 was published on February 21, 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 February 5, 2025; the record at its source may have been updated since.
Is CVE-2024-25124 actively exploited?
CVE-2024-25124 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-25124?
CVE-2024-25124 has a CVSS v3 base score of 9.4 (NVD).
How do I remediate CVE-2024-25124?
A fix for CVE-2024-25124 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-25124 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-25124

Explore →

Is Your Infrastructure Affected by CVE-2024-25124?

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

Book a Demo →Browse All CVEs