{"answers":{"affected":"3 open source packages ship an affected version, including code.gitea.io/gitea.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58419 exists.","fix":"Upgrade code.gitea.io/gitea to 1.26.4 or later.","what":"CVE-2026-58419 is a high-severity vulnerability in Gitea Open Source Git Server, published on 3 Jul 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-58419 and fix it if it is affected.\n\nWhat it is: CVE-2026-58419 is a high-severity vulnerability in Gitea Open Source Git Server, published on 3 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58419 exists.\n\nAffected packages and fixed versions:\n- code.gitea.io/gitea (Go): affected all versions; fixed in 1.26.4\n- code.gitea.io/gitea (Go): affected all versions; fixed in 1.26.4\n- code.gitea.io/gitea (Go): affected all versions; fixed in 1.26.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-58419/ (Markdown: https://insights.sbomify.com/CVE-2026-58419/index.md)","id":"CVE-2026-58419","markdown":"https://insights.sbomify.com/CVE-2026-58419/index.md","name":"CVE-2026-58419","record":{"aliases":["GHSA-44qc-pgvp-wx7v","GO-2026-6041"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Gitea Git Server","requires_auth":"none","summary":"Attackers can view private issue metadata via the Notification API even after access revocation, exposing sensitive repository information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Gitea","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Notification API leaks private issue metadata after access revocation","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Notification API leaks private issue metadata after access revocation","id":"CVE-2026-58419","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"Local File Inclusion via file:// URI in Migration Restore","id":"CVE-2026-58420"},"packages":[{"ecosystem":"Go","fixed":["1.26.4"],"introduced":["0"],"last_affected":[],"package":"code.gitea.io/gitea","purl":null,"source":"GHSA-44qc-pgvp-wx7v"},{"ecosystem":"Go","fixed":["1.26.4"],"introduced":["0"],"last_affected":[],"package":"code.gitea.io/gitea","purl":"pkg:golang/code.gitea.io/gitea","source":"GHSA-44qc-pgvp-wx7v"},{"ecosystem":"Go","fixed":["1.26.4"],"introduced":["0"],"last_affected":[],"package":"code.gitea.io/gitea","purl":"pkg:golang/code.gitea.io/gitea","source":"GO-2026-6041"}],"prev":{"headline":"SSRF via HTTP Redirect in Repository Migration","id":"CVE-2026-58418"},"products":["Gitea Open Source Git Server"],"published":"2026-07-03","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-06","vendors":["Gitea"]},"summary":"Attackers can view private issue metadata via the Notification API even after access revocation, exposing sensitive repository information.","url":"https://insights.sbomify.com/CVE-2026-58419/"}