Skip to main content
VulnerabilityPublished

CVE-2026-119285: Fiber · CORS wildcard origins matched without a dot boundary, allowing credentialed cross-origin reads

Affects github.com/gofiber/fiber/v2Source GCVE Database

0
Compare
Authoritative record:CVE-2026-119285· Medium 5.9

Not known to be exploited · CVSS 5.9 Medium : upgrade to 2.52.3 when convenient.

Data as of 31 Oct 2026, 02:06 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.9
Patch
Available – fixed in 2.52.3
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade github.com/gofiber/fiber/v2 to 2.52.3.

Affected software

ProductAffectedFixed in
Gogithub.com/gofiber/fiber/v2Affected
  • >=2.52.1 <2.52.3
Fixed in
  • 2.52.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Fiber to version 2.52.3 or later, where the CORS origin matching logic has been corrected to properly enforce dot boundaries and scheme checks. No other mitigation is required as the issue is fixed in these versions.

Description

A vulnerability in Fiber v2.52.1 and v2.52.2 CORS middleware allowed wildcard origins to be matched incorrectly without enforcing a dot boundary or scheme check. This caused origins with hosts ending in the base domain, but not actual subdomains (e.g., https://evil-example.com for https://*.example.com), to be reflected in Access-Control-Allow-Origin with credentials allowed. The issue was fixed in v2.52.3 by improving the origin matching logic.

References

Community reviews

Loading reviews…