{"answers":{"affected":"1 open source package ship an affected version, including gitea. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-89182 exists.","fix":"Upgrade gitea to 28.1.0 or later.","what":"CVE-2026-89182 is a medium-severity vulnerability in Gitea Gitea, published on 6 Oct 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-89182 and fix it if it is affected.\n\nWhat it is: CVE-2026-89182 is a medium-severity vulnerability in Gitea Gitea, published on 6 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-89182 exists.\n\nAffected packages and fixed versions:\n- gitea (Bitnami): affected from 1.27.0; 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-89182/ (Markdown: https://insights.sbomify.com/CVE-2026-89182/index.md)","id":"CVE-2026-89182","markdown":"https://insights.sbomify.com/CVE-2026-89182/index.md","name":"CVE-2026-89182","record":{"aliases":["BIT-gitea-2026-89182","GHSA-fx95-gwfc-grgc","MINI-m49g-5gp8-whmv","MINI-q7w6-pfm4-w84f"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Gitea Git hosting","requires_auth":"low_privilege","summary":"Attackers can bypass the FORCE_PRIVATE policy to make new repositories public when this specific configuration is enabled.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Gitea","cpe":[{"product":"gitea","vendor":"gitea"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"With `[repository] FORCE_PRIVATE = true`, Gitea creates new repositories as private, but the post-receive hook still applied the `repo.private=false` push option to an empty repository created by push. Any user who can create repositories could make their new repository public in violation of the instance policy. The default configuration is not affected.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Gitea push-to-create bypass of FORCE_PRIVATE policy","id":"CVE-2026-89182","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"gitea:gitea","products":["gitea:gitea"],"type":"security_feature_bypass","year":"2026"},"n_packages":1,"n_references":5,"next":{"headline":"Information disclosure in mpp","id":"CVE-2026-89186"},"packages":[{"ecosystem":"Bitnami","fixed":["28.1.0"],"introduced":["1.27.0"],"last_affected":[],"package":"gitea","purl":"pkg:bitnami/gitea","source":"BIT-gitea-2026-89182"}],"prev":{"headline":"Thinking Software Technology｜EFence - SQL Injection","id":"CVE-2026-89180"},"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-07","vendors":["Gitea"]},"summary":"Attackers can bypass the FORCE_PRIVATE policy to make new repositories public when this specific configuration is enabled.","url":"https://insights.sbomify.com/CVE-2026-89182/"}