CVE-2026-61630

MEDIUMPre-NVD 4.24.2—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 71% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
4.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

nginx ignition is a user interface for the nginx web server. In versions 2.33.0 through 2.35.0, any user that has enabled the OTP 2FA can have their TOTP reused during the standard 30 second validity window. Version 2.35.1 patches the issue.

CVSS v3
4.2
EG Score
4.2(medium)
EG Risk
19(Track)
EG Risk 19/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity42% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

September 21, 2026

Last Modified

September 24, 2026

Advisory Details (2)

Auto-updated Sep 21, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit

commit 8d35e1eb5dd6 (lucasdillmann/nginx-ignition)

Fix landed in lucasdillmann/nginx-ignition commit 8d35e1eb5dd6 — awaiting tagged release

https://github.com/lucasdillmann/nginx-ignition/commit/8d35e1eb5dd6a40fef94a45511fe08b0603af107
github Patch Available🟡 PoC Available

TOTP Reuse During Validity Window · Advisory · lucasdillmann/nginx-ignition · GitHub

https://github.com/lucasdillmann/nginx-ignition/security/advisories/GHSA-hf33-q6cf-c66f

Vendor Advisories for CVE-2026-61630(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/lucasdillmann/nginx-ignition—0.0.0-20260328015550-8d35e1eb5dd6—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 9× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-24 21:38 UTCEG score recompute
  2. 2026-09-23 23:22 UTCEG score recompute
  3. 2026-09-23 17:54 UTCEPSS rescore
  4. 2026-09-22 22:21 UTCEG score recompute
  5. 2026-09-21 21:23 UTCEG score recompute
  6. 2026-09-21 20:48 UTCEG score recompute
  7. 2026-09-21 15:22 UTCEG score recompute
  8. 2026-09-21 14:25 UTCEG score recompute
  9. 2026-09-21 14:25 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Same product

2 shown

Go:github.com/lucasdillmann/nginx-ignition

Frequently asked(5)

What is CVE-2026-61630?
CVE-2026-61630 is a medium vulnerability published on September 21, 2026. nginx ignition is a user interface for the nginx web server. In versions 2.33.0 through 2.35.0, any user that has enabled the OTP 2FA can have their TOTP reused during the standard 30 second validity window. Version 2.35.1 patches the issue.
When was CVE-2026-61630 disclosed?
CVE-2026-61630 was first published in the National Vulnerability Database on September 21, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61630 actively exploited?
CVE-2026-61630 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 70.8% of all scored CVEs.
What is the CVSS score of CVE-2026-61630?
CVE-2026-61630 has a CVSS v3 base score of 4.2 (NVD).
How do I remediate CVE-2026-61630?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61630, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-61630

Explore →

Is Your Infrastructure Affected by CVE-2026-61630?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs