Fiber has Insecure CORS Configuration, Allowing Wildcard Origin with Credentials

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

• CISA KEV Not listed.
• EPSS 0.0066, the 51st percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

1. 31 Oct 2026, 14:15 UTC First seen by agentprime
2. 31 Oct 2026, 14:15 UTC Confirmed by OSV

Sources

• GitHub Advisory Database: GHSA-fmg4-x8pw-hjhg
• OSV: GHSA-fmg4-x8pw-hjhg
• github.com/gofiber/fiber/security/advisories/GHSA-fmg4-x8pw-hjhg
• nvd.nist.gov/vuln/detail/CVE-2024-25124
• github.com/gofiber/fiber/commit/f0cd3b44b086544a37886232d0530601f2406c23
• codeql.github.com/codeql-query-help/javascript/js-cors-misconfiguration-for-credentials
• developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSNotSupportingCredentials
• fetch.spec.whatwg.org/#cors-protocol-and-credentials
• github.com/gofiber/fiber
• github.com/gofiber/fiber/releases/tag/v2.52.1
• saturncloud.io/blog/cors-cannot-use-wildcard-in-accesscontrolalloworigin-when-credentials-flag-is-true
• blog.portswigger.net/2016/10/exploiting-cors-misconfigurations-for.html

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.