Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
nginx ignition versions from 0.0.0-20260217145239-1cbfae0296f1 up to (not including) 0.0.0-20260328015550-8d35e1eb5dd6 accept a TOTP two-factor code more than once during its 30-second validity window. An attacker who captures or obtains a user's current one-time code, for example through traffic capture or phishing, could reuse it to log in before it expires. Upgrade to 0.0.0-20260328015550-8d35e1eb5dd6 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 4.2 | Medium | 3.1 | CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:N/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0038, the 32nd percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:12 UTC First seen by agentprime
- 31 Oct 2026, 14:12 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-hf33-q6cf-c66f
- OSV: GHSA-hf33-q6cf-c66f
- github.com/lucasdillmann/nginx-ignition/security/advisories/GHSA-hf33-q6cf-c66f
- nvd.nist.gov/vuln/detail/CVE-2026-61630
- github.com/pquerna/otp/issues/61
- github.com/lucasdillmann/nginx-ignition/pull/104
- github.com/lucasdillmann/nginx-ignition/commit/1cbfae0296f1b186158f5a294ec484060e00102e
- github.com/lucasdillmann/nginx-ignition/commit/8d35e1eb5dd6a40fef94a45511fe08b0603af107
- github.com/lucasdillmann/nginx-ignition
- github.com/lucasdillmann/nginx-ignition/releases/tag/2.35.1