Account access via reusable TOTP codes
Published Sep 21, 2026 · Updated Sep 21, 2026
Improper authentication in nginx ignition 2.33.0 through 2.35.0 allows remote authenticated users to reuse a captured TOTP. The authentication service validates a time-based code but does not record or reject that code after successful use, so a second request within the 30-second window is accepted. Exploitation requires an OTP-enabled account, its password, and a captured or phished current code; replay grants another session with that account's access.
Summary
What happened
Improper authentication in nginx ignition 2.33.0 through 2.35.0 allows remote authenticated users to reuse a captured TOTP. The authentication service validates a time-based code but does not record or reject that code after successful use, so a second request within the 30-second window is accepted. Exploitation requires an OTP-enabled account, its password, and a captured or phished current code; replay grants another session with that account's access.
The record
- CVE
- CVE-2026-61630
- Published
- Sep 21, 2026
- Updated
- Sep 21, 2026
- Vendor
- Lucas Dillmann
- Product
- nginx ignition
- Classifications
- CWE-287, T1556.006
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 21, 2026CVE publishedPublication date reported by the CVE source.
- Sep 21, 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=>= 2.33.0, < 2.35.1
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- TOTP reuse proof-of-concept videoproof of concept · demonstrated
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started