{"answers":{"affected":"3 open source packages ship an affected version, including code.gitea.io/gitea.","exploited":"There is no known exploitation of CVE-2026-26247 in the wild and no public exploit code.","fix":"Upgrade code.gitea.io/gitea to 1.25.5 or later.","what":"CVE-2026-26247 is a critical authentication bypass 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-26247 and fix it if it is affected.\n\nWhat it is: CVE-2026-26247 is a critical authentication bypass 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: There is no known exploitation of CVE-2026-26247 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.25.5\n- code.gitea.io/gitea (Go): affected all versions; fixed in 1.25.5\n- code.gitea.io/gitea (Go): affected all versions; fixed in 1.25.5\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-26247/ (Markdown: https://insights.sbomify.com/CVE-2026-26247/index.md)","id":"CVE-2026-26247","markdown":"https://insights.sbomify.com/CVE-2026-26247/index.md","name":"CVE-2026-26247","record":{"aliases":["GHSA-m5ch-ppfx-xv3v","GO-2026-6342"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Git server","requires_auth":"none","summary":"Attackers can bypass OAuth2 PKCE verification to obtain tokens without the correct verifier, potentially leading to unauthorized access.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Gitea","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"Gitea versions before 1.25.5 do not persist the OAuth2 PKCE S256 challenge method correctly during authorization, allowing token exchange without the expected verifier check.","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 OAuth2 PKCE S256 challenges are not enforced during token exchange","id":"CVE-2026-26247","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"Not used","id":"CVE-2026-26249"},"packages":[{"ecosystem":"Go","fixed":["1.25.5"],"introduced":["0"],"last_affected":[],"package":"code.gitea.io/gitea","purl":null,"source":"GHSA-m5ch-ppfx-xv3v"},{"ecosystem":"Go","fixed":["1.25.5"],"introduced":["0"],"last_affected":[],"package":"code.gitea.io/gitea","purl":"pkg:golang/code.gitea.io/gitea","source":"GHSA-m5ch-ppfx-xv3v"},{"ecosystem":"Go","fixed":["1.25.5"],"introduced":["0"],"last_affected":[],"package":"code.gitea.io/gitea","purl":"pkg:golang/code.gitea.io/gitea","source":"GO-2026-6342"}],"prev":{"headline":"Memory Exhaustion via Malformed PSD File Upload","id":"CVE-2026-26246"},"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-07","vendors":["Gitea"]},"summary":"Attackers can bypass OAuth2 PKCE verification to obtain tokens without the correct verifier, potentially leading to unauthorized access.","url":"https://insights.sbomify.com/CVE-2026-26247/"}