{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-120991 in the wild and no public exploit code.","exposure":"Only installations with a non-default setting turned on are exposed.","fix":"No fix has been published for CVE-2026-120991 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-120991 is a medium-severity business logic flaw vulnerability in Gitea, published on 15 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-120991 and fix it if it is affected.\n\nWhat it is: CVE-2026-120991 is a medium-severity business logic flaw vulnerability in Gitea, published on 15 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-120991 in the wild and no public exploit code.\nExposure: Only installations with a non-default setting turned on are exposed.\n\nAffected product: Gitea. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-120991/ (Markdown: https://insights.sbomify.com/CVE-2026-120991/index.md)","id":"CVE-2026-120991","markdown":"https://insights.sbomify.com/CVE-2026-120991/index.md","name":"CVE-2026-120991","record":{"aliases":["GHSA-q8pg-ggp9-rm9m"],"analysis":{"component_type":"web_application","exploitable_when_present":false,"fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Git hosting service","requires_auth":"low_privilege","requires_specific_call":false,"summary":"A Gitea user can make another owner's container blobs undownloadable by uploading identical content that failed upload cleanup.","user_interaction":"not_required","vuln_class":"business_logic","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"Gitea","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-460","name":"Improper Cleanup on Thrown Exception"}],"description":"When a container blob upload was rejected, for example because it exceeded a package size quota, the cleanup removed the blob from storage even if the same content already existed and was used by other packages. On an instance with a package quota configured, a user who can upload container images and has the exact content of another owner's package file or image layer could make it undownloadable. The cleanup now only removes blobs that the failed upload created.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Gitea deletion of shared container blobs on rejected uploads","id":"CVE-2026-120991","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":0,"n_references":5,"n_vendor_status":0,"next":{"headline":"NGINX ngx_stream_ssl_module vulnerability","id":"CVE-2026-120993"},"nickname":null,"packages":[],"prev":{"headline":"billboard.js before 4.1.3 allows an attacker to execute malicious JavaScript due to improper sanitization of series ids during legend template rendering.","id":"CVE-2026-120988"},"products":["Gitea"],"published":"2026-11-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-11-16","vendor_status":[],"vendors":["Gitea"]},"summary":"A Gitea user can make another owner's container blobs undownloadable by uploading identical content that failed upload cleanup.","url":"https://insights.sbomify.com/CVE-2026-120991/"}