Account takeover via unverified password changes
Published Mar 20, 2026 · Updated Mar 20, 2026
Improper authentication in Frigate before 0.17.0-beta1 allows remote authenticated users to take over accounts through password changes. The /users/{username}/password handler rewrites the authenticated user's password hash without verifying the current password, enforcing strength rules, or recording a change time used to reject older JWTs. A stolen valid session token is the gate; it can set a lasting password and remains usable after the victim resets the account password.
Summary
What happened
Improper authentication in Frigate before 0.17.0-beta1 allows remote authenticated users to take over accounts through password changes. The /users/{username}/password handler rewrites the authenticated user's password hash without verifying the current password, enforcing strength rules, or recording a change time used to reject older JWTs. A stolen valid session token is the gate; it can set a lasting password and remains usable after the victim resets the account password.
The record
- CVE
- CVE-2026-33124
- Published
- Mar 20, 2026
- Updated
- Mar 20, 2026
- Vendor
- Frigate, Inc.
- Product
- Frigate
- Classifications
- CWE-287, T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 20, 2026CVE publishedPublication date reported by the CVE source.
- Mar 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.17.0-beta1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo