Some CORS middleware allow untrusted origins
Priority LOW 38Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
### Impact Some CORS middleware (more specifically those created by specifying two or more origin patterns whose hosts share a proper suffix) incorrectly allow some untrusted origins, thereby opening the door to cross-origin attacks from the untrusted origins in question. For example, specifying origin patterns `https://foo.com` and `https://bar.com` (in that order) would yield a middleware that would incorrectly allow untrusted origin `https://barfoo.com`. ### Patches Patched in v0.9.0. ### Workarounds None.
Why it matters now
Fix Fixed github.com/jub0bs/fcors (Go): 0.9.0
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | github.com/jub0bs/fcors (Go) | before 0.9.0 | 0.9.0 | Patch available | GHSA-v84h-653v-4pq9 |
- github.com/jub0bs/fcors (Go) Vendor— Affected before 0.9.0 Fixed in 0.9.0 Patch available GHSA-v84h-653v-4pq9
Remediation
- Fix · GHSA-v84h-653v-4pq9 github.com/jub0bs/fcors (Go) Fixed in 0.9.0 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-v84h-653v-4pq9
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences