CVE-2025-24358: Github.com/gorilla/csrf Gorilla/csrf CSRF Vulnerability Due To Vulnerability

MODERATE
Advisory Identifier: GHSA-rq77-p4h8-4crw
CWE-352
Published
Advisory Summary

CVE-2025-24358 is a MODERATE gorilla/csrf csrf vulnerability due to vulnerability (CWE-352: Cross-Site Request Forgery (CSRF)) affecting Github.com/gorilla/csrf libraries in the Go ecosystem. The issue involves gorilla/csrf csrf vulnerability due to broken referer validation. Remediation is available by upgrading affected packages to version 1.7.3.

CVE-2025-24358 at a Glance

CVE Identifier CVE-2025-24358
GHSA Identifier GHSA-rq77-p4h8-4crw
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-352: Cross-Site Request Forgery (CSRF)
Affected Product Github.com/gorilla/csrf
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2025-24358

To remediate this vulnerability, upgrade all affected Github.com/gorilla/csrf dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/gorilla/csrf fixed: 1.7.3
Upgrade github.com/gorilla/csrf to 1.7.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/gorilla/csrf

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-24358, inspect your project dependencies for Github.com/gorilla/csrf:

inspect dependencies for github.com/gorilla/csrf

Analyze the terminal output to locate any version of Github.com/gorilla/csrf in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.7.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-352: Cross-Site Request Forgery (CSRF), where the web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. In Github.com/gorilla/csrf, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary gorilla/csrf is vulnerable to CSRF via form submission from origins that share a top level domain with the target origin. ### Details gorilla/csrf does not validate the Origin header against an allowlist. Its executes its validation of the Referer header for cross-origin requests only when it believes the request is being served over TLS. It determines this by inspecting the `r.URL.Scheme` value. However, this value is never populated for "server" requests [per the Go spec](https://pkg.go.dev/net/http#Request), and so this check does not run in practice. ``` // URL specifies either the URI being requested (for server // requests) or the URL to access (for client requests). // // For server requests, the URL is parsed from the URI // supplied on the Request-Line as stored in RequestURI. For // most requests, fields other than Path and RawQuery will be // empty. (See [RFC 7230, Section 5.3](https://rfc-editor.org/rfc/rfc7230.html#section-5.3)) // // For client requests, the URL's Host specifies the server to // connect to, while the Request's Host field optionally // specifies the Host header value to send in the HTTP // request. URL *[url](https://pkg.go.dev/net/url).[URL](https://pkg.go.dev/net/url#URL) ``` ### PoC - create trusted origin `target.example.test` protected with gorilla/csrf and served over TLS hosting form on `/submit` - create attacker origin `attack.example.test` served over TLS - attacker exfiltrates token & cookie combination from `target.example.test` - attacker sets exfiltrated cookie with `domain=.example.test and path=/submit` - as the cookie has a more specific path than `/` (the default for CSRF cookies) it will be sent first by the browser on submit to our target origin - submit form from `attack.example.test` with exfiltrated CSRF form token - observe valid form submission as `attack.example.test` Origin / Referer headers are not validated. ### Impact This vulnerability allows an attacker who has gained XSS on a subdomain or top level domain to perform authenticated form submissions against gorilla/csrf protected targets that share the same top level domain. This bug has existed in gorilla/csrf since its initial release in 2015.

CVE-2025-24358 Affected Github.com/gorilla/csrf Versions

1 component(s)
Fixed Versions:
1.7.3
Product / Package Ecosystem Affected Versions Fixed Version
github.com/gorilla/csrf
Go
< 1.7.3
1.7.3

References

Frequently Asked Questions

What is CVE-2025-24358?
CVE-2025-24358 is a security vulnerability in Github.com/gorilla/csrf involving gorilla/csrf CSRF vulnerability due to broken Referer validation under CWE-352: Cross-Site Request Forgery (CSRF).
Which Github.com/gorilla/csrf versions are affected?
Affected versions include releases prior to 1.7.3 across affected packages: github.com/gorilla/csrf.
What version fixes CVE-2025-24358?
Upgrading to 1.7.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/gorilla/csrf affected?
Yes, github.com/gorilla/csrf is affected in releases prior to 1.7.3. Upgrade your dependency to 1.7.3 or later.
What CWE is associated with CVE-2025-24358?
CVE-2025-24358 is classified under CWE-352: Cross-Site Request Forgery (CSRF) (The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.).
How can I check Go dependencies for CVE-2025-24358?
Run the dependency tree command: 'inspect dependencies for github.com/gorilla/csrf'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rq77-p4h8-4crw",
  "modified" : "2025-05-01T12:31:16Z",
  "published" : "2025-04-14T15:26:07Z",
  "aliases" : [ "CVE-2025-24358" ],
  "summary" : "gorilla/csrf CSRF vulnerability due to broken Referer validation",
  "details" : "### Summary\n\ngorilla/csrf is vulnerable to CSRF via form submission from origins that share a top level domain with the target origin.\n\n### Details\n\ngorilla/csrf does not validate the Origin header against an allowlist. Its executes its validation of the Referer header for cross-origin requests only when it believes the request is being served over TLS. It determines this by inspecting the `r.URL.Scheme` value. However, this value is never populated for \"server\" requests [per the Go spec](https://pkg.go.dev/net/http#Request), and so this check does not run in practice. \n```\n\t// URL specifies either the URI being requested (for server\n\t// requests) or the URL to access (for client requests).\n\t//\n\t// For server requests, the URL is parsed from the URI\n\t// supplied on the Request-Line as stored in RequestURI.  For\n\t// most requests, fields other than Path and RawQuery will be\n\t// empty. (See [RFC 7230, Section 5.3](https://rfc-editor.org/rfc/rfc7230.html#section-5.3))\n\t//\n\t// For client requests, the URL's Host specifies the server to\n\t// connect to, while the Request's Host field optionally\n\t// specifies the Host header value to send in the HTTP\n\t// request.\n\tURL *[url](https://pkg.go.dev/net/url).[URL](https://pkg.go.dev/net/url#URL)\n```\n\n### PoC\n\n- create trusted origin `target.example.test` protected with gorilla/csrf and served over TLS hosting form on `/submit`\n- create attacker origin `attack.example.test` served over TLS\n- attacker exfiltrates token & cookie combination from `target.example.test` \n- attacker sets exfiltrated cookie with `domain=.example.test and path=/submit`\n  - as the cookie has a more specific path than `/` (the default for CSRF cookies) it will be sent first by the browser on submit to our target origin\n- submit form from `attack.example.test` with exfiltrated CSRF form token\n- observe valid form submission as `attack.example.test` Origin / Referer headers are not validated. \n\n### Impact\n\nThis vulnerability allows an attacker who has gained XSS on a subdomain or top level domain to perform authenticated form submissions against gorilla/csrf protected targets that share the same top level domain.\n\nThis bug has existed in gorilla/csrf since its initial release in 2015.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/gorilla/csrf"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.7.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/gorilla/csrf/security/advisories/GHSA-rq77-p4h8-4crw"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-24358"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/gorilla/csrf/commit/9dd6af1f6d30fc79fb0d972394deebdabad6b5eb"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/gorilla/csrf"
  }, {
    "type" : "WEB",
    "url" : "https://lists.debian.org/debian-lts-announce/2025/05/msg00002.html"
  }, {
    "type" : "WEB",
    "url" : "https://pkg.go.dev/vuln/GO-2025-3607"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-352" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-04-14T15:26:07Z",
    "nvd_published_at" : "2025-04-15T19:16:07Z"
  }
}