nginx ignition has TOTP Reuse During Validity Window

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps lucasdillmann/nginx-ignition (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for lucasdillmann/nginx-ignition.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Sep 21, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 21, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 21, 2026

Sources and claim methodology

• GitHub security advisorygithub.com
• GitHub security advisorygithub.com
• GitHub security advisorygithub.com

Related CVEs

• nginx ignition has Unauthenticated Admin Account Creation via Onboarding Race ConditionSame lucasdillmann/nginx-ignition package
• nginx ignition has ParseAcceptLanguage `_` separator bypass that enables ~75x CPU amplification via Accept-Language header in i18nMiddlewareSame lucasdillmann/nginx-ignition package
• Hatchet - Unauthenticated OAuth state CSRF / login-CSRF via empty-state collision in ValidateOAuthStateAlso CWE-287
• UVdesk core-framework before 1.1.7 Stored XSS via SwiftMailerSame generic ecosystem
• UVdesk core-framework before 1.1.7 Authorization Bypass via Saved ReplySame generic ecosystem
• UVdesk core-framework before 1.1.7 Privilege Escalation via editAgentSame generic ecosystem