ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2025-47909

Hosts listed in TrustedOrigins implicitly allow requests from the corresponding HTTP origins, allowing network MitMs to perform CSRF attacks.

Published Aug 29, 2025 · catalog updated Oct 19, 2026 · Hosts listed in TrustedOrigins

Last checked Oct 23, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2025-47909. EPSS is 0.17%. Act only if a listed version of Hosts listed in TrustedOrigins is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Hosts listed in TrustedOrigins).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.17%
Remediation
Vendor / distro source
Affected products
vendor github.com/gorilla/csrf github.com/gorilla/csrf patch: 0

Hosts listed in TrustedOrigins implicitly allow requests from the corresponding HTTP origins, allowing network MitMs to perform CSRF attacks. After the CVE-2025-24358 fix, a network attacker that places a form at http://example.com can't get it to submit to https://example.com because the Origin header is checked with sameOrigin against a synthetic URL. However, if a host is added to TrustedOrigins, both its HTTP and HTTPS origins will be allowed, because the schema of the synthetic URL is ignored and only the host is checked. For example, if an application is hosted on https://example.com and adds example.net to TrustedOrigins, a network attacker can serve a form at http://example.net to perform the attack. Applications should migrate to net/http.CrossOriginProtection, introduced in Go 1.25. If that is not an option, a backport is available as a module at filippo.io/csrf, and a drop-in replacement for the github.com/gorilla/csrf API is available at filippo.io/csrf/gorilla.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor github.com/gorilla/csrf github.com/gorilla/csrf patch: 0patch: 0

How to fix CVE-2025-47909

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-47909. EPSS is 0.17%. Act only if a listed version of Hosts listed in TrustedOrigins is installed.

Which versions are affected?

Compare what you have installed with github.com/gorilla/csrf github.com/gorilla/csrf patch: 0 patch: 0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-346. EPSS 0.17%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Aug 29, 2025 · NIST NVD

    Detected

    Hosts listed in TrustedOrigins implicitly allow requests from the corresponding HTTP origins, allowing network MitMs to perform CSRF attacks. After the CVE-2025-24358 fix, a network attacker that places a form at http://example.com can't get it to submit to https://example.com because the Origin header is checked with sameOrigin against a synthetic URL. However, if a host is added to TrustedOrigin

  2. Oct 19, 2026 · NIST NVD

    Updated

    Hosts listed in TrustedOrigins implicitly allow requests from the corresponding HTTP origins, allowing network MitMs to perform CSRF attacks. After the CVE-2025-24358 fix, a network attacker that places a form at http://example.com can't get it to submit to https://example.com because the Origin header is checked with sameOrigin against a synthetic URL. However, if a host is added to TrustedOrigin

Sources

  • CVE.orgVulnerability recordCVE-2025-47909

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-47909

    30-day exploitation probability 0.17%

    first.org
  • EUVDVulnerability recordEUVD-2025-26212

    Hosts listed in TrustedOrigins implicitly allow requests from the corresponding HTTP origins, allowing network MitMs to perform CSRF attacks. After the CVE-2025-24358 fix, a network attacker that places a form at http://example.com can't get it to submit to https://example.com be

    euvd.enisa.europa.eu
  • NIST NVDVulnerability recordCVE-2025-47909

    Hosts listed in TrustedOrigins implicitly allow requests from the corresponding HTTP origins, allowing network MitMs to perform CSRF attacks. After the CVE-2025-24358 fix, a network attacker that places a form at http://example.com can't get it to submit to https://example.com be

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 23, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSOct 23, 2026
  • EUVDOct 22, 2026
  • CVE.orgOct 21, 2026
  • NIST NVDOct 19, 2026