# nginx ignition has TOTP Reuse During Validity Window

Advisory record · `GHSA-hf33-q6cf-c66f`

- **Identifiers:** `GHSA-hf33-q6cf-c66f` · `CVE-2026-61630` · `GO-2026-6537`
- **State:** Confirmed
- **Severity:** CVSS 4.2 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 21 Sept 2026
- **Updated:** 28 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 21 Sept 2026, 21:47 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/lucasdillmann/nginx-ignition` (Go): affected `>=0.0.0-20260217145239-1cbfae0296f1, <0.0.0-20260328015550-8d35e1eb5dd6`; fixed in `0.0.0-20260328015550-8d35e1eb5dd6`

## 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.

Written 1 Nov 2026.

## 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

- 4.2 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:N/A:N`, from 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](https://osv.dev/vulnerability/GHSA-hf33-q6cf-c66f)

## Sources

- [GitHub Advisory Database: GHSA-hf33-q6cf-c66f](https://github.com/advisories/GHSA-hf33-q6cf-c66f)
- [OSV: GHSA-hf33-q6cf-c66f](https://osv.dev/vulnerability/GHSA-hf33-q6cf-c66f)
- <https://github.com/lucasdillmann/nginx-ignition/security/advisories/GHSA-hf33-q6cf-c66f>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-61630>
- <https://github.com/pquerna/otp/issues/61>
- <https://github.com/lucasdillmann/nginx-ignition/pull/104>
- <https://github.com/lucasdillmann/nginx-ignition/commit/1cbfae0296f1b186158f5a294ec484060e00102e>
- <https://github.com/lucasdillmann/nginx-ignition/commit/8d35e1eb5dd6a40fef94a45511fe08b0603af107>
- <https://github.com/lucasdillmann/nginx-ignition>
- <https://github.com/lucasdillmann/nginx-ignition/releases/tag/2.35.1>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-hf33-q6cf-c66f>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-hf33-q6cf-c66f/>. Everything for agents: <https://agentprime.io/llms.txt>.