Fiber has Insecure CORS Configuration, Allowing Wildcard Origin with Credentials

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.4 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

EPSS

• CVE-2024-25124: 0.66% estimated exploitation activity in the next 30 days; percentile 51.41 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. Impact 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. Proof of Concept The code in cors.go allows setting a wildcard in the AllowOrigins while having AllowCredentials set to true, which could lead to various vulnerabilities. Potential Solution Here is a potential solution to ensure the CORS configuration is secure: Workarounds For the meantime, users are advised to manually validate the CORS configurations in their implementation to ensure that they do not allow a…

Published by the source

22 Feb 2024, 18:25 UTC

Last modified by the source

15 Mar 2026, 05:07 UTC

Source last checked

26 Oct 2026, 15:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-fmg4-x8pw-hjhg

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-25124

Advisory: Fiber has Insecure CORS Configuration, Allowing Wildcard Origin with Credentials
IDs: CVE-2024-25124, GHSA-fmg4-x8pw-hjhg
Record: https://patchnext.com/advisories/cve-2024-25124 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/gofiber/fiber/v2 2.52.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/gofiber/fiber/v2: affected < 2.52.1; fixed in 2.52.1

## Suggested inspection (read-only)
- Go github.com/gofiber/fiber/v2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/gofiber/fiber/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-fmg4-x8pw-hjhg (GitHub-reviewed advisory GHSA-fmg4-x8pw-hjhg lists affected ranges: Go github.com/gofiber/fiber/v2 >=0 <2.52.1)

Commands are suggestions: review each one before running it.