{"answers":{"affected":"4 open source packages ship an affected version, including github.com/go-gitea/gitea, gitea and code.gitea.io/gitea. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-20897 in the wild and no public exploit code.","fix":"Upgrade github.com/go-gitea/gitea to 1.25.4 or later.","what":"CVE-2026-20897 is a critical missing authorization vulnerability in Gitea Gitea, published on 22 Jan 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-20897 and fix it if it is affected.\n\nWhat it is: CVE-2026-20897 is a critical missing authorization vulnerability in Gitea Gitea, published on 22 Jan 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-20897 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/go-gitea/gitea (Go): affected all versions; fixed in 1.25.4\n- github.com/go-gitea/gitea (Go): affected all versions; fixed in 1.25.4\n- gitea (Bitnami): affected all versions; fixed in 1.25.4\n- code.gitea.io/gitea (Go): affected all versions; fixed in 1.25.4\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-20897/ (Markdown: https://insights.sbomify.com/CVE-2026-20897/index.md)","id":"CVE-2026-20897","markdown":"https://insights.sbomify.com/CVE-2026-20897/index.md","name":"CVE-2026-20897","record":{"aliases":["BIT-gitea-2026-20897","GHSA-393c-qgvj-3xph","GHSA-rrq5-r9h5-pc7c","GO-2026-4363"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Git server","requires_auth":"none","summary":"An attacker with write access to one repository can delete Git LFS locks in other repositories due to missing ownership validation.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Gitea","cpe":[{"product":"gitea","vendor":"gitea"}],"cvss":{"score":9.1,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"Gitea does not properly validate repository ownership when deleting Git LFS locks. A user with write access to one repository may be able to delete LFS locks belonging to other repositories.","ecosystems":["Bitnami","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":"Gitea Git LFS Lock Deletion Broken Access Control (Cross-Repo IDOR)","id":"CVE-2026-20897","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"gitea:gitea","products":["gitea:gitea"],"type":"missing_authorization","year":"2026"},"n_packages":4,"n_references":5,"next":{"headline":"Privilege escalation in in Alias Checking Trusted Module for some Intel(R) Xeon(R) processors may allow an escalation of privilege. Startup code and SMM adversary with a privileged user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (high), integrity (high) and availability (none) impacts.","id":"CVE-2026-20898"},"packages":[{"ecosystem":"Bitnami","fixed":["1.25.4"],"introduced":["0"],"last_affected":[],"package":"gitea","purl":"pkg:bitnami/gitea","source":"BIT-gitea-2026-20897"},{"ecosystem":"Go","fixed":["1.25.4"],"introduced":["0"],"last_affected":[],"package":"code.gitea.io/gitea","purl":"pkg:golang/code.gitea.io/gitea","source":"GO-2026-4363"},{"ecosystem":"Go","fixed":["1.25.4"],"introduced":["0"],"last_affected":[],"package":"github.com/go-gitea/gitea","purl":null,"source":"GHSA-393c-qgvj-3xph"},{"ecosystem":"Go","fixed":["1.25.4"],"introduced":["0"],"last_affected":[],"package":"github.com/go-gitea/gitea","purl":"pkg:golang/github.com/go-gitea/gitea","source":"GHSA-393c-qgvj-3xph"}],"prev":{"headline":"Gitea Docker image trusts spoofable reverse-proxy headers by default","id":"CVE-2026-20896"},"products":["Gitea Open Source Git Server"],"published":"2026-01-22","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":"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":"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-15","vendors":["Gitea"]},"summary":"An attacker with write access to one repository can delete Git LFS locks in other repositories due to missing ownership validation.","url":"https://insights.sbomify.com/CVE-2026-20897/"}