{"answers":{"affected":"1 open source package ship an affected version, including gitea. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-97208 in the wild and no public exploit code.","fix":"Upgrade gitea to 28.1.0 or later.","what":"CVE-2026-97208 is a medium-severity missing authorization vulnerability in Gitea Gitea, published on 6 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-97208 and fix it if it is affected.\n\nWhat it is: CVE-2026-97208 is a medium-severity missing authorization vulnerability in Gitea Gitea, published on 6 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-97208 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- gitea (Bitnami): affected all versions; fixed in 28.1.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-97208/ (Markdown: https://insights.sbomify.com/CVE-2026-97208/index.md)","id":"CVE-2026-97208","markdown":"https://insights.sbomify.com/CVE-2026-97208/index.md","name":"CVE-2026-97208","record":{"aliases":["BIT-gitea-2026-97208","GHSA-8hhh-mqpg-jpxc","MINI-mcg5-h772-2mr6","MINI-qxvq-m8f7-mxv7"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Gitea self-hosted Git","requires_auth":"high_privilege","summary":"Repository admins bypass site-wide push mirror restrictions via API, potentially exfiltrating code to unauthorized remotes.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Gitea","cpe":[{"product":"gitea","vendor":"gitea"}],"cvss":{"score":4.9,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"The Gitea API endpoint for creating push mirrors (`POST /api/v1/repos/{owner}/{repo}/push_mirrors`) checked only whether mirroring was enabled and not the `[mirror] DISABLE_NEW_PUSH` setting that the web interface enforces. A repository administrator could therefore create new push mirrors on instances where the site administrator had disabled them. A push mirror pushes all refs of the repository to a remote chosen by the caller, on each commit or on a schedule.","ecosystems":["Bitnami"],"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 push mirror API bypass of DISABLE_NEW_PUSH policy","id":"CVE-2026-97208","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"gitea:gitea","products":["gitea:gitea"],"type":"missing_authorization","year":"2026"},"n_packages":1,"n_references":5,"next":{"headline":"Monta monta.app Insufficient Session Expiration","id":"CVE-2026-97212"},"packages":[{"ecosystem":"Bitnami","fixed":["28.1.0"],"introduced":["0"],"last_affected":[],"package":"gitea","purl":"pkg:bitnami/gitea","source":"BIT-gitea-2026-97208"}],"prev":{"headline":"DNS-over-QUIC (DoQ) path-migration can lead to use-after-free on multi-threaded deployments.","id":"CVE-2026-97206"},"products":["Gitea"],"published":"2026-10-06","related":[{"cvss_score":9.8,"headline":"Gitea Code Injection","id":"CVE-2026-60004","kev_date_added":"2026-08-25","published":"2026-08-26"},{"cvss_score":9.8,"headline":"Gitea WebAuthn bypass during OAuth and OIDC sign-in","id":"CVE-2026-73278","kev_date_added":null,"published":"2026-10-06"},{"cvss_score":9.8,"headline":"Gitea fork workflow approval bypass through maintainer-triggered events","id":"CVE-2026-94205","kev_date_added":null,"published":"2026-10-06"},{"cvss_score":9.8,"headline":"Gitea vulnerable to Argument Injection","id":"CVE-2022-42968","kev_date_added":null,"published":"2022-10-16"},{"cvss_score":9.8,"headline":"Improper Privilege Management in Gitea","id":"CVE-2021-45330","kev_date_added":null,"published":"2022-02-09"},{"cvss_score":9.8,"headline":"Reuse of one time passwords allowed in Gitea","id":"CVE-2021-45331","kev_date_added":null,"published":"2022-02-09"},{"cvss_score":9.8,"headline":"Capture-replay in Gitea","id":"CVE-2021-45327","kev_date_added":null,"published":"2022-02-08"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-07","vendors":["Gitea"]},"summary":"Repository admins bypass site-wide push mirror restrictions via API, potentially exfiltrating code to unauthorized remotes.","url":"https://insights.sbomify.com/CVE-2026-97208/"}