Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Go package

github.com/justinas/nosurf

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.0GoPublished

    nosurf vulnerable to CSRF due to non-functional same-origin request checks

    CVE-2025-46721 · GHSA-w9hf-35q4-vcjw

    Affected
    • Go github.com/justinas/nosurf < 1.2.0
    Fixed in
    1.2.0· Vendor fix available
    Issue
    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…

    Recommended action: Upgrade to 1.2.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 7.5GoPublished

    nosurf vulnerable to improper input validation

    CVE-2020-36564 · GHSA-5x84-q523-vvwr

    Affected
    • Go github.com/justinas/nosurf < 1.1.1
    Fixed in
    1.1.1· Vendor fix available
    Issue
    Due to improper validation of caller input, validation is silently disabled if the provided expected token is malformed, causing any user supplied token to be considered valid.

    Recommended action: Upgrade to 1.1.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →