github.com/jub0bs/fcors
View on Github
Activity
- Latest release
- 1y ago
- Total releases
- 16
- Cadence
- ~2 months
- Last 12 months
- 0
Reach
- Stars
- —
Details
- First release
- Dec 21, 2022
| Version | Released | |
|---|---|---|
v0.10.0
minor
|
v0.10.0
minor
Dependencies (1)
|
|
v0.9.2
patch
|
v0.9.2
patch
Dependencies (1)
|
|
v0.9.1
patch
|
v0.9.1
patch
Dependencies (1)
|
|
v0.9.0
minor
|
v0.9.0
minor
Dependencies (1)
|
|
v0.8.0
minor
1 CVE
GO-2024-2812
GHSA-v84h-653v-4pq9
May 21, 2024
Some CORS middleware allow untrusted origins in github.com/jub0bs/fcors 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". Fixed in
0.9.0
References Updated Feb 04, 2026 · Source: OSV.dev |
v0.8.0
minor
Dependencies (1)
|
|
v0.7.0
minor
1 CVE
GO-2024-2812
GHSA-v84h-653v-4pq9
May 21, 2024
Some CORS middleware allow untrusted origins in github.com/jub0bs/fcors 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". Fixed in
0.9.0
References Updated Feb 04, 2026 · Source: OSV.dev |
v0.7.0
minor
Dependencies (1)
|
|
v0.6.0
minor
1 CVE
GO-2024-2812
GHSA-v84h-653v-4pq9
May 21, 2024
Some CORS middleware allow untrusted origins in github.com/jub0bs/fcors 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". Fixed in
0.9.0
References Updated Feb 04, 2026 · Source: OSV.dev |
v0.6.0
minor
Dependencies (2)
|
|
v0.5.1
patch
1 CVE
GO-2024-2812
GHSA-v84h-653v-4pq9
May 21, 2024
Some CORS middleware allow untrusted origins in github.com/jub0bs/fcors 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". Fixed in
0.9.0
References Updated Feb 04, 2026 · Source: OSV.dev |
v0.5.1
patch
Dependencies (2)
|
|
v0.5.0
minor
1 CVE
GO-2024-2812
GHSA-v84h-653v-4pq9
May 21, 2024
Some CORS middleware allow untrusted origins in github.com/jub0bs/fcors 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". Fixed in
0.9.0
References Updated Feb 04, 2026 · Source: OSV.dev |
v0.5.0
minor
Dependencies (2)
|
|
v0.4.0
minor
1 CVE
GO-2024-2812
GHSA-v84h-653v-4pq9
May 21, 2024
Some CORS middleware allow untrusted origins in github.com/jub0bs/fcors 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". Fixed in
0.9.0
References Updated Feb 04, 2026 · Source: OSV.dev |
v0.4.0
minor
Dependencies (2)
|
|
v0.3.1
patch
1 CVE
GO-2024-2812
GHSA-v84h-653v-4pq9
May 21, 2024
Some CORS middleware allow untrusted origins in github.com/jub0bs/fcors 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". Fixed in
0.9.0
References Updated Feb 04, 2026 · Source: OSV.dev |
v0.3.1
patch
Dependencies (2)
|
|
v0.3.0
minor
1 CVE
GO-2024-2812
GHSA-v84h-653v-4pq9
May 21, 2024
Some CORS middleware allow untrusted origins in github.com/jub0bs/fcors 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". Fixed in
0.9.0
References Updated Feb 04, 2026 · Source: OSV.dev |
v0.3.0
minor
Dependencies (2)
|
|
v0.2.0
minor
1 CVE
GO-2024-2812
GHSA-v84h-653v-4pq9
May 21, 2024
Some CORS middleware allow untrusted origins in github.com/jub0bs/fcors 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". Fixed in
0.9.0
References Updated Feb 04, 2026 · Source: OSV.dev |
v0.2.0
minor
Dependencies (2)
|
|
v0.1.1
patch
1 CVE
GO-2024-2812
GHSA-v84h-653v-4pq9
May 21, 2024
Some CORS middleware allow untrusted origins in github.com/jub0bs/fcors 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". Fixed in
0.9.0
References Updated Feb 04, 2026 · Source: OSV.dev |
v0.1.1
patch
Dependencies (2)
|
|
v0.1.0
initial
1 CVE
GO-2024-2812
GHSA-v84h-653v-4pq9
May 21, 2024
Some CORS middleware allow untrusted origins in github.com/jub0bs/fcors 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". Fixed in
0.9.0
References Updated Feb 04, 2026 · Source: OSV.dev |
v0.1.0
initial
Dependencies (2)
|
|
v0.1.0-beta1
pre
1 CVE
GO-2024-2812
GHSA-v84h-653v-4pq9
May 21, 2024
Some CORS middleware allow untrusted origins in github.com/jub0bs/fcors 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". Fixed in
0.9.0
References Updated Feb 04, 2026 · Source: OSV.dev |
v0.1.0-beta1
pre
Dependencies (2)
|