{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-123009 in the wild and no public exploit code.","exposure":"An affected version is exposed as installed. No special setting or call is needed.","fix":"No fix has been published for CVE-2026-123009 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-123009 is a medium-severity missing authorization 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-123009 and fix it if it is affected.\n\nWhat it is: CVE-2026-123009 is a medium-severity missing authorization 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-123009 in the wild and no public exploit code.\nExposure: An affected version is exposed as installed. No special setting or call is needed.\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-123009/ (Markdown: https://insights.sbomify.com/CVE-2026-123009/index.md)","id":"CVE-2026-123009","markdown":"https://insights.sbomify.com/CVE-2026-123009/index.md","name":"CVE-2026-123009","record":{"aliases":["GHSA-9vh6-6hgj-j5m5"],"analysis":{"component_type":"web_application","exploitable_when_present":false,"fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Git hosting service","requires_auth":"low_privilege","requires_specific_call":false,"summary":"Users who lost access to a Gitea repository can keep copying its branches into their fork and read the code; Gitea administrators should care.","user_interaction":"not_required","vuln_class":"missing_authorization","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"Gitea","component":null,"cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"When a file is edited in a fork through the web editor, Gitea can first copy a branch from the base repository into the fork. That copy did not check whether the user may read the base repository's code. A user who had forked a repository and later lost access to it, for example after it was made private or they were removed as a collaborator, could keep copying its current branches into their fork and read them. The copy now requires read access to the code of the base repository.","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 base repository code disclosure through the web editor in forks","id":"CVE-2026-123009","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"main_cpe":null,"main_fixed":[],"main_package":null,"n_packages":0,"n_references":5,"n_vendor_status":0,"next":{"headline":"@twilio-labs/netlify-okta-auth through 1.0.2 relies on an unverified iss claim.","id":"CVE-2026-123010"},"nickname":null,"packages":[],"prev":{"headline":"NGINX ngx_http_v2_module vulnerability","id":"CVE-2026-123007"},"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","text_fixes":[],"updated":"2026-11-16","vendor_status":[],"vendors":["Gitea"]},"summary":"Users who lost access to a Gitea repository can keep copying its branches into their fork and read the code; Gitea administrators should care.","url":"https://insights.sbomify.com/CVE-2026-123009/"}