# CVE-2026-107271: Gophish through 0.12.1 Login Rate Limit Bypass via X-Forwarded-For Spoofing

> Attackers can bypass login rate limits in Gophish by spoofing IP headers, enabling unlimited password guessing and credential stuffing attacks.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-hxwc-4ggw-27w5

## What is CVE-2026-107271?

CVE-2026-107271 is a medium-severity vulnerability in gophish, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Gophish through 0.12.1 contains a rate limit bypass vulnerability that allows unauthenticated attackers to evade /login throttling by spoofing X-Forwarded-For or X-Real-IP headers. Attackers can send a different forwarded address per request so the limiter keyed on rewritten RemoteAddr never triggers, enabling unlimited password guessing and credential stuffing.

Weakness: CWE-348 (Use of Less Trusted Source)

## Which versions are affected by CVE-2026-107271?


## How do I fix CVE-2026-107271?

No fix has been published for CVE-2026-107271 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-107271 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107271 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107271 and fix it if it is affected.

What it is: CVE-2026-107271 is a medium-severity vulnerability in gophish, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107271 exists.

Affected product: gophish. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-107271/ (Markdown: https://insights.sbomify.com/CVE-2026-107271/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107271
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107271
- OSV: https://osv.dev/vulnerability/CVE-2026-107271

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-107271/
Summaries are generated and may contain mistakes; the official description above is the record.