{"answers":{"affected":"3 open source packages ship an affected version, including code.gitea.io/gitea and gitea.dev.","exploited":"There is no known exploitation of CVE-2026-59766 in the wild and no public exploit code.","fix":"Upgrade code.gitea.io/gitea to 1.27.0 or later.","what":"CVE-2026-59766 is a medium-severity vulnerability in Gitea, published on 14 Oct 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-59766 and fix it if it is affected.\n\nWhat it is: CVE-2026-59766 is a medium-severity vulnerability in Gitea, published on 14 Oct 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-59766 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- code.gitea.io/gitea (Go): affected all versions; fixed in 1.27.0\n- code.gitea.io/gitea (Go): affected all versions; fixed in 1.27.0\n- gitea.dev (Go): affected all versions; fixed in 1.27.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-59766/ (Markdown: https://insights.sbomify.com/CVE-2026-59766/index.md)","id":"CVE-2026-59766","markdown":"https://insights.sbomify.com/CVE-2026-59766/index.md","name":"CVE-2026-59766","record":{"aliases":["GHSA-qf2f-qh6p-7v89","GO-2026-6071","MINI-hhgx-cffh-3x62","MINI-jgwv-38gf-9whg"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Gitea Git hosting","requires_auth":"low_privilege","summary":"Attackers with revoked access can retrieve private repository metadata and issue titles via starred and tracked-time API endpoints.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Gitea","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-284","name":"Improper Access Control"}],"description":"Gitea's starred-repository and tracked-time API endpoints do not re-check current repository permissions before returning data associated with the requesting user. A user whose access to a private repository has been revoked can still retrieve repository metadata through /api/v1/user/starred and private issue titles through /api/v1/user/times. The disclosure depends on relationships or tracked-time entries created before access was revoked.","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":"Gitea private repository metadata disclosure after access revocation","id":"CVE-2026-59766","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"Hardcoded credentials in FA-50","id":"CVE-2026-59769"},"packages":[{"ecosystem":"Go","fixed":["1.27.0"],"introduced":["0"],"last_affected":[],"package":"code.gitea.io/gitea","purl":null,"source":"GHSA-qf2f-qh6p-7v89"},{"ecosystem":"Go","fixed":["1.27.0"],"introduced":["0"],"last_affected":[],"package":"code.gitea.io/gitea","purl":"pkg:golang/code.gitea.io/gitea","source":"GHSA-qf2f-qh6p-7v89"},{"ecosystem":"Go","fixed":["1.27.0"],"introduced":["0"],"last_affected":[],"package":"gitea.dev","purl":"pkg:golang/gitea.dev","source":"GO-2026-6071"}],"prev":{"headline":"SSRF via Migration Asset Downloads Bypasses hostmatcher — Reads Internal Files and Cloud Metadata","id":"CVE-2026-59765"},"products":["Gitea"],"published":"2026-10-14","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-10-14","vendors":["Gitea"]},"summary":"Attackers with revoked access can retrieve private repository metadata and issue titles via starred and tracked-time API endpoints.","url":"https://insights.sbomify.com/CVE-2026-59766/"}