{"answers":{"affected":"3 open source packages ship an affected version, including code.gitea.io/gitea and gitea.dev.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58511 exists.","fix":"Upgrade code.gitea.io/gitea to 1.27.0 or later.","what":"CVE-2026-58511 is a low-severity vulnerability in Gitea Open Source Git Server, published on 13 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-58511 and fix it if it is affected.\n\nWhat it is: CVE-2026-58511 is a low-severity vulnerability in Gitea Open Source Git Server, published on 13 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58511 exists.\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-58511/ (Markdown: https://insights.sbomify.com/CVE-2026-58511/index.md)","id":"CVE-2026-58511","markdown":"https://insights.sbomify.com/CVE-2026-58511/index.md","name":"CVE-2026-58511","record":{"aliases":["GHSA-3r5c-2xxx-h872","GO-2026-6040","MINI-3f44-6hhm-phcr","MINI-75j2-wccf-w42g"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Gitea Git Server","requires_auth":"high_privilege","summary":"Attackers can retrieve webhook authorization headers in plaintext via the API, exposing sensitive credentials in Gitea Git Server.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Gitea","cpe":[],"cvss":{"score":2.7,"severity":"low","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Webhook Authorization Header Returned in Plaintext via API","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":"Webhook Authorization Header Returned in Plaintext via API","id":"CVE-2026-58511","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"Blocked users can create and edit WikiLambda objects","id":"CVE-2026-58517"},"packages":[{"ecosystem":"Go","fixed":["1.27.0"],"introduced":["0"],"last_affected":[],"package":"code.gitea.io/gitea","purl":null,"source":"GHSA-3r5c-2xxx-h872"},{"ecosystem":"Go","fixed":["1.27.0"],"introduced":["0"],"last_affected":[],"package":"code.gitea.io/gitea","purl":"pkg:golang/code.gitea.io/gitea","source":"GHSA-3r5c-2xxx-h872"},{"ecosystem":"Go","fixed":["1.27.0"],"introduced":["0"],"last_affected":[],"package":"gitea.dev","purl":"pkg:golang/gitea.dev","source":"GO-2026-6040"}],"prev":{"headline":"Gitea: GHSA-8fwc-qjw5-rvgp ClearRepoWatches fix not applied to API EditRepo path — sister code path retains stale watches on public-\u003eprivate","id":"CVE-2026-58510"},"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-13","vendors":["Gitea"]},"summary":"Attackers can retrieve webhook authorization headers in plaintext via the API, exposing sensitive credentials in Gitea Git Server.","url":"https://insights.sbomify.com/CVE-2026-58511/"}