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

Published Aug 28, 2026
·
Updated

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.

Affected Software

1 affected component
Gophish Gophish<0.12.1

Event History

Aug 28, 2026
CVE Published
via MITRE·04:18 PM
Data Sourced
via MITRE·04:18 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this issue?

Gophish installations through version 0.12.1 are affected if an attacker has a valid API key for an account that has been locked or is required to change its password.

2

What does an attacker need to exploit the bypass?

The attacker needs a valid API key. No user interaction is required, and the issue is reachable over the network.

3

What access does the bypass provide?

A valid API key can continue to provide full API access despite account lockout or a forced password-change requirement. The reported impact includes high confidentiality and integrity impact.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203