Fiber has Insecure CORS Configuration, Allowing Wildcard Origin with Credentials
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA and GitHub. Impact type from CWE-346.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| gofiber | fiber | before 2.52.1 | 2.52.1 | Patch available | CNA |
| — | github.com/gofiber/fiber/v2 (Go) | before 2.52.1 | 2.52.1 | Patch available | GHSA-fmg4-x8pw-hjhg |
- fiber Vendorgofiber Affected before 2.52.1 Fixed in 2.52.1 Patch available CNA
- github.com/gofiber/fiber/v2 (Go) Vendor— Affected before 2.52.1 Fixed in 2.52.1 Patch available GHSA-fmg4-x8pw-hjhg
Remediation
- Fix · CNA fiber (gofiber) Fixed in 2.52.1
- Fix · GHSA-fmg4-x8pw-hjhg github.com/gofiber/fiber/v2 (Go) Fixed in 2.52.1 Advisory →
Vendor assessments
Timeline
- 2026-10-02 Threatist record created from CVE-2024-25124
- 2026-10-03 Alias added: GHSA-fmg4-x8pw-hjhg
- 2026-10-13 EPSS moved to the 50th–90th percentile
References
Exploit 2
Other 6
- https://codeql.github.com/codeql-query-help/javascript/js-cors-misconfiguration-for-credentials
- https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSNotSupportingCredentials
- https://fetch.spec.whatwg.org/#cors-protocol-and-credentials
- https://github.com/gofiber/fiber/releases/tag/v2.52.1
- https://saturncloud.io/blog/cors-cannot-use-wildcard-in-accesscontrolalloworigin-when-credentials-flag-is-true
- https://github.com/gofiber/fiber
More gofiber Fiber vulnerabilities
- TI-2025-34555 Fiber Susceptible to Crash via `BodyParser` Due to Unvalidated Large Slice Index in Decoder CVSS 4.0HIGH 8.7
- TI-2025-30446 Fiber panics when fiber.Ctx.BodyParser parses invalid range index CVSS 4.0HIGH 7.7
- TI-2026-23477 github.com/gofiber/fiber/v3 cache middleware can mix responses across query parameters CVSS 3.1MEDIUM 6.5
- TI-2026-20922 Fiber has a Denial of Service Vulnerability via Route Parameter Overflow CVSS 4.0MEDIUM 5.5
- TI-2026-30834 Fiber: XSS in AutoFormat Content Negotiation CVSS 4.0MEDIUM 5.3
- TI-2026-38670 Fiber: HSTS header never set in helmet middleware due to incorrect protocol check CVSS 3.1MEDIUM 4.8
Sources
- CVE-2024-25124 · CVE Program
- CVE-2024-25124 · NVD
- FIRST EPSS
- GHSA-fmg4-x8pw-hjhg · GitHub Advisory Database · CC BY 4.0
- CVE-2024-25124 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences