{"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-58442 in the wild and no public exploit code.","fix":"Upgrade code.gitea.io/gitea to 1.27.0 or later.","what":"CVE-2026-58442 is a medium-severity server-side request forgery vulnerability in Gitea Open Source Git Server, published on 13 Aug 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-58442 and fix it if it is affected.\n\nWhat it is: CVE-2026-58442 is a medium-severity server-side request forgery vulnerability in Gitea Open Source Git Server, published on 13 Aug 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-58442 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-58442/ (Markdown: https://insights.sbomify.com/CVE-2026-58442/index.md)","id":"CVE-2026-58442","markdown":"https://insights.sbomify.com/CVE-2026-58442/index.md","name":"CVE-2026-58442","record":{"aliases":["GHSA-h2x6-g7q6-344v","GO-2026-6058","MINI-cm58-vc2f-gjhv","MINI-w78r-4chr-8cf4"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Gitea Git Server","requires_auth":"low_privilege","summary":"Attackers can bypass DNS allow-lists during repository migration to perform Server-Side Request Forgery and access internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","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:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Repository migration SSRF via multi-answer DNS allow-list bypass","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":"Repository migration SSRF via multi-answer DNS allow-list bypass","id":"CVE-2026-58442","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"Public-only repository tokens can update private PR head branches","id":"CVE-2026-58443"},"packages":[{"ecosystem":"Go","fixed":["1.27.0"],"introduced":["0"],"last_affected":[],"package":"code.gitea.io/gitea","purl":null,"source":"GHSA-h2x6-g7q6-344v"},{"ecosystem":"Go","fixed":["1.27.0"],"introduced":["0"],"last_affected":[],"package":"code.gitea.io/gitea","purl":"pkg:golang/code.gitea.io/gitea","source":"GHSA-h2x6-g7q6-344v"},{"ecosystem":"Go","fixed":["1.27.0"],"introduced":["0"],"last_affected":[],"package":"gitea.dev","purl":"pkg:golang/gitea.dev","source":"GO-2026-6058"}],"prev":{"headline":"SSRF in restore-repo via unsanitized pull_request.yml Head.CloneURL","id":"CVE-2026-58441"},"products":["Gitea Open Source Git Server"],"published":"2026-08-13","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-08-14","vendors":["Gitea"]},"summary":"Attackers can bypass DNS allow-lists during repository migration to perform Server-Side Request Forgery and access internal resources.","url":"https://insights.sbomify.com/CVE-2026-58442/"}