# CVE-2026-82269: Gophish Account Lockout and Forced Password Change Bypassable via API Key

> Attackers with valid API keys can bypass account lockout and forced password change controls in Gophish, retaining unauthorized access.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-p62h-c2g7-8x23

## What is CVE-2026-82269?

CVE-2026-82269 is a high-severity vulnerability in gophish, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Gophish through 0.12.1 fails to enforce account lockout and password change requirements in the API authentication middleware. Attackers with valid API keys can bypass these security controls and retain full API access even when their account is locked or password change is required.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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


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

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

## Is CVE-2026-82269 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82269 is a high-severity vulnerability in gophish, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82269 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-82269/ (Markdown: https://insights.sbomify.com/CVE-2026-82269/index.md)
```

## Sources

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

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