Skip to content
Fencer Intel
medium 4.2

CVE-2026-61630 json

nginx ignition has TOTP Reuse During Validity Window

published last mo. modified last mo. also GHSA-hf33-q6cf-c66f , GO-2026-6537 , EUVD-2026-83922

cvss
4.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 32%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/lucasdillmann/nginx-ignition 0.0.0-20260328015550-8d35e1eb5dd6

Is CVE-2026-61630 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last mo.

Exploit prediction

0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 4.2 CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:N/A:N
GitHub 3.1 4.2 CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/lucasdillmann/nginx-ignition
>=0.0.0-20260217145239-1cbfae0296f1, <0.0.0-20260328015550-8d35e1eb5dd6
0.0.0-20260328015550-8d35e1eb5dd6

Affected products

  • lucasdillmann nginx-ignition

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.