How severe is GHSA-w9hf-35q4-vcjw?

No CVSS score has been assigned to GHSA-w9hf-35q4-vcjw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w9hf-35q4-vcjw?

GHSA-w9hf-35q4-vcjw affects the following packages: github.com/justinas/nosurf (Go). Ecosystems affected: Go.

How do I fix GHSA-w9hf-35q4-vcjw?

Update github.com/justinas/nosurf to 1.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w9hf-35q4-vcjw is resolved across your whole dependency graph.

How do I detect GHSA-w9hf-35q4-vcjw in my Go dependencies?

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

How do I mitigate GHSA-w9hf-35q4-vcjw if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-w9hf-35q4-vcjw actively exploited in the wild?

No public exploit code has been indexed for GHSA-w9hf-35q4-vcjw 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.

What is the EPSS score for GHSA-w9hf-35q4-vcjw?

GHSA-w9hf-35q4-vcjw has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 16th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-w9hf-35q4-vcjw?

GHSA-w9hf-35q4-vcjw is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-w9hf-35q4-vcjw published, and has it been updated?

GHSA-w9hf-35q4-vcjw was published on May 14, 2025 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

nosurf vulnerable to CSRF due to non-functional same-origin request checksGHSA-w9hf-35q4-vcjw

Fix: justinas/nosurf@ec9bb77

GHSA-w9hf-35q4-vcjw is a Cross-Site Request Forgery (CSRF) vulnerability in github.com/justinas/nosurf. A fix is available for github.com/justinas/nosurf — see the affected versions and patch details below.

Also known asCVE-2025-46721GO-2025-3683

Published

May 14, 2025

Updated

Feb 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-w9hf-35q4-vcjw.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs16th percentile — riskier than 16% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/justinas/nosurf

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

This vulnerability allows an attacker who controls content on the target site, or on a subdomain of the target site (either via XSS, or otherwise) to bypass Cross-Site Request Forgery checks and issue requests on user's behalf.

Details

Due to misuse of the Go net/http library, nosurf categorizes all incoming requests as plain-text HTTP requests, in which case the Referer header is not checked to have the same origin as the target webpage.

If the attacker has control over HTML contents on either the target website (e.g. example.com), or on a website hosted on a subdomain of the target (e.g. attacker.example.com), they will also be able to manipulate cookies set for the target website. By acquiring the secret CSRF token from the cookie, or overriding the cookie with a new token known to the attacker, attacker.example.com is able to craft cross-site requests to example.com.

Patches

A patch for the issue was released in nosurf 1.2.0.

Workarounds

In lieu of upgrading to a patched version of nosurf, users may additionally use another HTTP middleware to ensure that a non-safe HTTP request is coming from the same origin (e.g. by requiring a Sec-Fetch-Site: same-origin header in the request).

References

https://github.com/advisories/GHSA-rq77-p4h8-4crw https://github.com/justinas/nosurf-cve-2025-46721 https://www.cve.org/CVERecord?id=CVE-2025-46721 https://github.com/justinas/nosurf/releases/tag/v1.2.0

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/justinas/nosurf`	all versions	1.2.0`go get github.com/justinas/nosurf@v1.2.0`

Affected Products

1 product · 1 configurations

Application

nosurfnosurf_project

< 1.2.0

range

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/justinas/nosurf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/justinas/nosurf to 1.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w9hf-35q4-vcjw is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Impact This vulnerability allows an attacker who controls content on the target site, or on a subdomain of the target site (either via XSS, or otherwise) to bypass Cross-Site Request Forgery checks and issue requests on user's behalf. ### Details Due to misuse of the Go `net/http` library, nosurf categorizes all incoming requests as plain-text HTTP requests, in which case the `Referer` header is not checked to have the same origin as the target webpage. If the attacker has control over HTML contents on either the target website (e.g. `example.com`), or on a website hosted on a subdomai

O3 Security · Impact-Aware SCA

Is GHSA-w9hf-35q4-vcjw in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works