Security fix · CVE-2026-119285
Fiber: CORS wildcard origins matched without a dot boundary, allowing credentialed cross-origin reads
Published Oct 30, 2026 · catalog updated Oct 30, 2026 · Fiber: CORS wildcard origins
Last checked Nov 6, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-119285. EPSS is 0.13%. Act only if a listed version of Fiber: CORS wildcard origins is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (Fiber: CORS wildcard origins).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Medium5.9
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.13%
- Remediation
- Version ranges on file
- Affected products
- Go github.com/gofiber/fiber/v2 · go github.com/gofiber/fiber/v2 · golang github.com
### Summary In v2.52.1 and v2.52.2 the CORS middleware matched a wildcard origin such as by suffix only, without a dot boundary and without comparing the scheme. Any origin whose host ends with the base domain, for example or , was reflected in , together with when is enabled. v2.52.3 replaced the matcher (#2915) and is not affected. The report was filed against v2.52.15, where the dot boundary holds; see "Other versions" below. ### Details v2.52.1 introduced in (f0cd3b44, part of the fix for GHSA-fmg4-x8pw-hjhg). It strips scheme and port from both sides and then checks only the suffix, with , so the character before the suffix is never checked: v2.52.3 (1aac6f61, #2915) replaced it with a scheme-aware prefix/suffix split that keeps the leading dot in the suffix ( ). ### Proof of concept Request with , as a GET and as a preflight ( with ): | Version | | | |---|---|---| | v2.52.0 | not allowed | not allowed | | v2.52.1, v2.52.2 | reflected, | reflected, | | v2.52.3 to v2.52.16 | not allowed | not allowed | ### Impact An app that configures a wildcard-subdomain with lets any page on a domain that ends with the base domain (for example for ) read authenticated responses cross-origin. Fixed in v2.52.3; upgrade to the latest v2 release. ### Other versions All v2 releases before v2.52.16 also accepted origins with empty labels ( , ), and v2.52.3 to v2.52.15 mis-parsed a wildcard entry after a comma and a space ( ). No registrable domain produces such an origin, so these are hardening rather than part of this advisory. They are fixed in v2.52.16 (#4792).
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Go github.com/gofiber/fiber/v22.52.1 → 2.52.3
- go github.com/gofiber/fiber/v2>= 2.52.1, <= 2.52.2
- golang github.comversion unspecified
How to fix CVE-2026-119285
Upgrade
CVE-2026-119285 lists a fix boundary at 2.52.3. Compare the installed build with that boundary before you change production.
Version check
Affected <= 2.52.2
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-119285. EPSS is 0.13%. Act only if a listed version of Fiber: CORS wildcard origins is installed.
Which versions are affected?
Compare what you have installed with 2.52.1 → 2.52.3, >= 2.52.1, <= 2.52.2. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-346; CWE-942: Permissive Cross-domain Policy with Untrusted Domains. EPSS 0.13%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 30, 2026 · GitHub Advisory Database
Detected
### Summary In v2.52.1 and v2.52.2 the CORS middleware matched a wildcard origin such as by suffix only, without a dot boundary and without comparing the scheme. Any origin whose host ends with the base domain, for example or , was reflected in , together with when is enabled. v2.52.3 replaced the matcher (#2915) and is not affected. The report was filed against v2.52.15, where the dot boundary ho
Oct 30, 2026 · GitHub Advisory Database
Fix available
github.com/gofiber/fiber/v2 fixed in 2.52.3
Oct 30, 2026 · GitHub Advisory Database
Fix available
github.com/gofiber/fiber/v2 fixed in 2.52.3
Oct 30, 2026 · GitHub Advisory Database
Updated
### Summary In v2.52.1 and v2.52.2 the CORS middleware matched a wildcard origin such as by suffix only, without a dot boundary and without comparing the scheme. Any origin whose host ends with the base domain, for example or , was reflected in , together with when is enabled. v2.52.3 replaced the matcher (#2915) and is not affected. The report was filed against v2.52.15, where the dot boundary ho
Sources
- CVE.orgVulnerability recordCVE-2026-119285
Official CVE identifier
cve.org - GitHub Advisory DatabasePackage advisoryGHSA-g5jq-qmqr-qrwf
GitHub Advisory Database record mirrored by OSV.
github.com - GitLab Advisory DatabasePackage advisoryCVE-2026-119285
In v2.52.1 and v2.52.2 the CORS middleware matched a wildcard origin such as https://*.example.com by suffix only, without a dot boundary and without comparing the scheme. Any origin whose host ends with the base domain, for example https://evil-example.com or http://notexample.com , was reflected in Access-Control-Allow-Origin, together with Access-Control-Allow-Credentials: true when AllowCreden
advisories.gitlab.com - Go Vulnerability DatabasePackage advisoryGHSA-g5jq-qmqr-qrwf
Fiber: CORS wildcard origins matched without a dot boundary, allowing credentialed cross-origin reads
osv.dev - OpenSSF OSV / OSV ScannerPackage advisoryGHSA-g5jq-qmqr-qrwf
Fiber: CORS wildcard origins matched without a dot boundary, allowing credentialed cross-origin reads
osv.dev
References
Freshness
Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- Go Vulnerability DatabaseNov 4, 2026
- GitLab Advisory DatabaseNov 3, 2026
- GitHub Advisory DatabaseNov 2, 2026
- OpenSSF OSV / OSV ScannerNov 2, 2026
- CVE.orgOct 31, 2026