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


- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026

## What is CVE-2026-119285?

CVE-2026-119285 is a medium-severity vulnerability in gofiber fiber, published on 29 Oct 2026. 

### Official description

Fiber is an Express inspired web framework written in Go. From 2.52.1 until 2.52.3, the CORS middleware's validateDomain wildcard matcher in middleware/cors/utils.go strips the scheme and checks only a host suffix without requiring a dot boundary. An application configured with a wildcard-subdomain AllowOrigins value and AllowCredentials enabled can reflect an unrelated attacker-controlled origin whose host merely ends with the configured base domain. A user who visits that origin can expose authenticated cross-origin responses to the attacker's page; empty-label origins and later comma-space parsing hardening are outside this advisory. This issue is fixed in version 2.52.3.

Weakness: CWE-942 (Permissive Cross-domain Security Policy with Untrusted Domains), CWE-346 (Origin Validation Error)

## Which versions are affected by CVE-2026-119285?


## How do I fix CVE-2026-119285?

No fix has been published for CVE-2026-119285 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119285 being exploited?

There is no known exploitation of CVE-2026-119285 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119285 and fix it if it is affected.

What it is: CVE-2026-119285 is a medium-severity vulnerability in gofiber fiber, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119285 in the wild and no public exploit code.

Affected product: gofiber fiber. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119285/ (Markdown: https://insights.sbomify.com/CVE-2026-119285/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119285
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119285
- OSV: https://osv.dev/vulnerability/CVE-2026-119285

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119285/
Summaries are generated and may contain mistakes; the official description above is the record.