{"answers":{"affected":"3 open source packages ship an affected version, including github.com/lucasdillmann/nginx-ignition.","exploited":"There is no known exploitation of CVE-2026-61630 in the wild and no public exploit code.","fix":"Upgrade github.com/lucasdillmann/nginx-ignition to 0.0.0-20260328015550-8d35e1eb5dd6 or later.","what":"CVE-2026-61630 is a medium-severity authentication bypass vulnerability in lucasdillmann nginx-ignition, published on 21 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-61630 and fix it if it is affected.\n\nWhat it is: CVE-2026-61630 is a medium-severity authentication bypass vulnerability in lucasdillmann nginx-ignition, published on 21 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-61630 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/lucasdillmann/nginx-ignition (Go): affected from 0.0.0-20260217145239-1cbfae0296f1; fixed in 0.0.0-20260328015550-8d35e1eb5dd6\n- github.com/lucasdillmann/nginx-ignition (Go): affected from 0.0.0-20260217145239-1cbfae0296f1; fixed in 0.0.0-20260328015550-8d35e1eb5dd6\n- github.com/lucasdillmann/nginx-ignition (Go): affected from 0.0.0-20260217145239-1cbfae0296f1; fixed in 0.0.0-20260328015550-8d35e1eb5dd6\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-61630/ (Markdown: https://insights.sbomify.com/CVE-2026-61630/index.md)","id":"CVE-2026-61630","markdown":"https://insights.sbomify.com/CVE-2026-61630/index.md","name":"CVE-2026-61630","record":{"aliases":["GHSA-hf33-q6cf-c66f","GO-2026-6537"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"nginx web server UI","requires_auth":"high_privilege","summary":"Attackers can reuse TOTP codes within the validity window to bypass two-factor authentication in nginx ignition.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"nginx ignition has TOTP Reuse During Validity Window","id":"CVE-2026-61630","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"PyMdown Extensions: Path traversal in the b64 extension lets \u003cimg src\u003e read files outside base_path","id":"CVE-2026-61632"},"packages":[{"ecosystem":"Go","fixed":["0.0.0-20260328015550-8d35e1eb5dd6"],"introduced":["0.0.0-20260217145239-1cbfae0296f1"],"last_affected":[],"package":"github.com/lucasdillmann/nginx-ignition","purl":null,"source":"GHSA-hf33-q6cf-c66f"},{"ecosystem":"Go","fixed":["0.0.0-20260328015550-8d35e1eb5dd6"],"introduced":["0.0.0-20260217145239-1cbfae0296f1"],"last_affected":[],"package":"github.com/lucasdillmann/nginx-ignition","purl":"pkg:golang/github.com/lucasdillmann/nginx-ignition","source":"GHSA-hf33-q6cf-c66f"},{"ecosystem":"Go","fixed":["0.0.0-20260328015550-8d35e1eb5dd6"],"introduced":["0.0.0-20260217145239-1cbfae0296f1"],"last_affected":[],"package":"github.com/lucasdillmann/nginx-ignition","purl":"pkg:golang/github.com/lucasdillmann/nginx-ignition","source":"GO-2026-6537"}],"prev":{"headline":"nginx ignition has ParseAcceptLanguage `_` separator bypass that enables ~75x CPU amplification via Accept-Language header in i18nMiddleware","id":"CVE-2026-61629"},"products":["nginx-ignition"],"published":"2026-09-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-21","vendors":["lucasdillmann"]},"summary":"Attackers can reuse TOTP codes within the validity window to bypass two-factor authentication in nginx ignition.","url":"https://insights.sbomify.com/CVE-2026-61630/"}