CVE-2026-61630 nginx ignition has TOTP Reuse During Validity Window

Medium 4.2 Published Updated

Attackers can reuse TOTP codes within the validity window to bypass two-factor authentication in nginx ignition.

Exploited in the wild
Not known
Login needed
An administrator
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2026-61630?

CVE-2026-61630 is a medium-severity authentication bypass vulnerability in lucasdillmann nginx-ignition, published on 21 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

Official description

nginx ignition is a user interface for the nginx web server. In versions 2.33.0 through 2.35.0, any user that has enabled the OTP 2FA can have their TOTP reused during the standard 30 second validity window. Version 2.35.1 patches the issue.

Weakness: CWE-287

Which versions are affected by CVE-2026-61630?

3 open source packages ship an affected version, including github.com/lucasdillmann/nginx-ignition.

PackageAffectedFixed in
github.com/lucasdillmann/nginx-ignition GoFrom 0.0.0-20260217145239-1cbfae0296f10.0.0-20260328015550-8d35e1eb5dd6
github.com/lucasdillmann/nginx-ignition GoFrom 0.0.0-20260217145239-1cbfae0296f10.0.0-20260328015550-8d35e1eb5dd6
github.com/lucasdillmann/nginx-ignition GoFrom 0.0.0-20260217145239-1cbfae0296f10.0.0-20260328015550-8d35e1eb5dd6

How do I fix CVE-2026-61630?

Upgrade github.com/lucasdillmann/nginx-ignition to 0.0.0-20260328015550-8d35e1eb5dd6 or later.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is CVE-2026-61630 being exploited?

There is no known exploitation of CVE-2026-61630 in the wild and no public exploit code.

Sources

Also known as GHSA-hf33-q6cf-c66f, GO-2026-6537.

Is CVE-2026-61630 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free