How severe is GHSA-vhxv-fg4m-p2w8?

GHSA-vhxv-fg4m-p2w8 has a CVSS score of 9.3/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-vhxv-fg4m-p2w8?

GHSA-vhxv-fg4m-p2w8 affects the following packages: github.com/jub0bs/cors (Go). Ecosystems affected: Go.

How do I fix GHSA-vhxv-fg4m-p2w8?

Update github.com/jub0bs/cors to 0.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vhxv-fg4m-p2w8 is resolved across your whole dependency graph.

How do I detect GHSA-vhxv-fg4m-p2w8 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/jub0bs/cors, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-vhxv-fg4m-p2w8 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-vhxv-fg4m-p2w8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-vhxv-fg4m-p2w8 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-vhxv-fg4m-p2w8 published, and has it been updated?

GHSA-vhxv-fg4m-p2w8 was published on May 3, 2024 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

CRITICAL severity

Some CORS middleware allow untrusted originsGHSA-vhxv-fg4m-p2w8

CRITICALFix: jub0bs/cors@5bc0648

GHSA-vhxv-fg4m-p2w8 is a critical-severity (CVSS 9.3) vulnerability in github.com/jub0bs/cors. A fix is available for github.com/jub0bs/cors — see the affected versions and patch details below.

Also known asGO-2024-2813

Published

May 3, 2024

Updated

Feb 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Feb 4, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/jub0bs/cors

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.1.3.

Workarounds

None.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/jub0bs/cors`	all versions	0.1.3`go get github.com/jub0bs/cors@v0.1.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/jub0bs/cors, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/jub0bs/cors to 0.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vhxv-fg4m-p2w8 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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.1.3. ### Workarounds None.

O3 Security · Impact-Aware SCA

Is GHSA-vhxv-fg4m-p2w8 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works