Authentication Bypass in github.com/lucasdillmann/nginx-ignition (CVE-2026-61630)
Summary
Authentication bypass in github.com/lucasdillmann/nginx-ignition (CVE-2026-61630). Confidential information can be exposed externally. Mitigation: upgrade to 0.0.0-20260328015550-8d35e1eb5dd6 or later.
Original description
The description as published by the source.
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 of attack. This disrupts one layer of the defense-in-depth model surrounding 2FA.
Similar CVEs
- CVE-2025-6014
- [CVE-2025-55003](h…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-61630 has been found in github.com/lucasdillmann/nginx-ignition.
Confidential information can be exposed externally. CVSS score: 4.2/10.
What to do: upgrade github.com/lucasdillmann/nginx-ignition to 0.0.0-20260328015550-8d35e1eb5dd6 or later.
If unsure, ask your IT team or search "github.com/lucasdillmann/nginx-ignition CVE-2026-61630" on the vendor's site.
CVE-2026-61630 (github.com/lucasdillmann/nginx-ignition) — CWE-287 / CVSS v3 4.2
Attack vector: remote (network-reachable)
Patched: 0.0.0-20260328015550-8d35e1eb5dd6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Authentication bypass (CWE-287) exists in github.com/lucasdillmann/nginx-ignition.
Check the vendor advisory for the affected versions of github.com/lucasdillmann/nginx-ignition.
Severity: Medium (CVSS 4.2/10). Confidential information can be exposed externally.
Update to 0.0.0-20260328015550-8d35e1eb5dd6.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/lucasdillmann/nginx-ignition' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/lucasdillmann/nginx-ignition' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/lucasdillmann/nginx-ignitionを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/lucasdillmann/nginx-ignition to 0.0.0-20260328015550-8d35e1eb5dd6ステージング環境で 0.0.0-20260328015550-8d35e1eb5dd6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com
- web github.com
- web github.com
- web github.com