nginx ignition has TOTP Reuse During Validity Window

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.2 · CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-61630: 0.38% estimated exploitation activity in the next 30 days; percentile 32.11 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Any user that has enabled the OTP 2FA can have their TOTP reused during the standard 30 second validity window. Details The https://github.com/pquerna/otp package doesn't include checking for already used TOTPs within its the validity window. This requires each application that uses the package to implement their own method of tracking and verifying that codes can't be reused. Section 6.5.1 within the Authentication section of the OWASP ASVS recommends multiple checks, some of which involving TOTPs: Verify that lookup secrets, out-of-band authentication requests or codes, and time-based one-time passwords (TOTPs) are only successfully usable once. The OWASP WSTG also references this as one of their checks to look for: Can the OTPs be used more than once? PoC https://github.com/user-attachments/assets/86a43374-39bf-4d61-8f6d-5cc440c99a1e Impact Any user who uses 2FA could be impacted if their traffic is able to be captured, they're phished/social engineered, or other methods…

Published by the source

21 Sep 2026, 21:47 UTC

Last modified by the source

28 Sep 2026, 17:00 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-hf33-q6cf-c66f

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6537

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-hf33-q6cf-c66f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-61630

Advisory: nginx ignition has TOTP Reuse During Validity Window
IDs: CVE-2026-61630, GHSA-hf33-q6cf-c66f
Record: https://patchnext.com/advisories/cve-2026-61630 (revision 3, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/lucasdillmann/nginx-ignition 0.0.0-20260328015550-8d35e1eb5dd6. A vendor fix does not mean a deployment is fixed.

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

## Suggested inspection (read-only)
- Go github.com/lucasdillmann/nginx-ignition: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/lucasdillmann/nginx-ignition.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-hf33-q6cf-c66f (OSV record GHSA-hf33-q6cf-c66f lists affected ranges: Go github.com/lucasdillmann/nginx-ignition >=0.0.0-20260217145239-1cbfae0296f1 <0.0.0-20260328015550-8d35e1eb5dd6 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6537 (OSV record GO-2026-6537 lists affected ranges: Go github.com/lucasdillmann/nginx-ignition >=0.0.0-20260217145239-1cbfae0296f1 <0.0.0-20260328015550-8d35e1eb5dd6 (fixed))
- Verified: https://github.com/advisories/GHSA-hf33-q6cf-c66f (GitHub-reviewed advisory GHSA-hf33-q6cf-c66f lists affected ranges: Go github.com/lucasdillmann/nginx-ignition >=0.0.0-20260217145239-1cbfae0296f1 <0.0.0-20260328015550-8d35e1eb5dd6)

Commands are suggestions: review each one before running it.