{"answers":{"affected":"1 open source package ship an affected version, including gitea. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-96404 in the wild and no public exploit code.","fix":"Upgrade gitea to 28.0.0 or later.","what":"CVE-2026-96404 is a high-severity authentication bypass vulnerability in Gitea Gitea, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-96404 and fix it if it is affected.\n\nWhat it is: CVE-2026-96404 is a high-severity authentication bypass vulnerability in Gitea Gitea, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-96404 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- gitea (Bitnami): affected all versions; fixed in 28.0.0\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-96404/ (Markdown: https://insights.sbomify.com/CVE-2026-96404/index.md)","id":"CVE-2026-96404","markdown":"https://insights.sbomify.com/CVE-2026-96404/index.md","name":"CVE-2026-96404","record":{"aliases":["BIT-gitea-2026-96404","GHSA-9h7g-h754-c8x2","MINI-g7fp-pr7m-c43g","MINI-h83v-58w6-48jh"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Gitea web installer","requires_auth":"none","summary":"Attackers can bypass authentication and gain administrative access by submitting the installer form with an existing username when the install lock is disabled.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Gitea","cpe":[{"product":"gitea","vendor":"gitea"}],"cvss":{"score":8.1,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"When Gitea's web installer is reachable against a database that already contains users, such as after `INSTALL_LOCK` has been reset to `false`, submitting the install form with an administrator username matching an existing account issued an authenticated session for that account without verifying its password. If the account is an administrator, the session grants full administrative access, including changing the account's password. Databases with a single user also did not require the reinstall confirmation.","ecosystems":["Bitnami"],"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":"Gitea installer authentication bypass for existing accounts","id":"CVE-2026-96404","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"gitea:gitea","products":["gitea:gitea"],"type":"auth_bypass","year":"2026"},"n_packages":1,"n_references":4,"next":{"headline":"Aggregate DNS name chained pointer decompression work leads to degradation of service.","id":"CVE-2026-96405"},"packages":[{"ecosystem":"Bitnami","fixed":["28.0.0"],"introduced":["0"],"last_affected":[],"package":"gitea","purl":"pkg:bitnami/gitea","source":"BIT-gitea-2026-96404"}],"prev":{"headline":"USBX PIMA/MTP host class reads past its receive buffer when a device over-reports its object handle count","id":"CVE-2026-96402"},"products":["Gitea"],"published":"2026-10-06","related":[{"cvss_score":9.8,"headline":"Gitea Code Injection","id":"CVE-2026-60004","kev_date_added":"2026-08-25","published":"2026-08-26"},{"cvss_score":9.8,"headline":"Gitea WebAuthn bypass during OAuth and OIDC sign-in","id":"CVE-2026-73278","kev_date_added":null,"published":"2026-10-06"},{"cvss_score":9.8,"headline":"Gitea fork workflow approval bypass through maintainer-triggered events","id":"CVE-2026-94205","kev_date_added":null,"published":"2026-10-06"},{"cvss_score":9.8,"headline":"Gitea vulnerable to Argument Injection","id":"CVE-2022-42968","kev_date_added":null,"published":"2022-10-16"},{"cvss_score":9.8,"headline":"Improper Privilege Management in Gitea","id":"CVE-2021-45330","kev_date_added":null,"published":"2022-02-09"},{"cvss_score":9.8,"headline":"Reuse of one time passwords allowed in Gitea","id":"CVE-2021-45331","kev_date_added":null,"published":"2022-02-09"},{"cvss_score":9.8,"headline":"Capture-replay in Gitea","id":"CVE-2021-45327","kev_date_added":null,"published":"2022-02-08"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"total"},"state":"PUBLISHED","updated":"2026-10-07","vendors":["Gitea"]},"summary":"Attackers can bypass authentication and gain administrative access by submitting the installer form with an existing username when the install lock is disabled.","url":"https://insights.sbomify.com/CVE-2026-96404/"}