{"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-104633 in the wild and no public exploit code.","fix":"Upgrade gitea to 28.1.0 or later.","what":"CVE-2026-104633 is a medium-severity denial of service 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-104633 and fix it if it is affected.\n\nWhat it is: CVE-2026-104633 is a medium-severity denial of service 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: There is no known exploitation of CVE-2026-104633 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-104633/ (Markdown: https://insights.sbomify.com/CVE-2026-104633/index.md)","id":"CVE-2026-104633","markdown":"https://insights.sbomify.com/CVE-2026-104633/index.md","name":"CVE-2026-104633","record":{"aliases":["BIT-gitea-2026-104633","GHSA-jj5r-9rpc-8h6h","MINI-3g88-h77w-4vgf","MINI-57xj-5qch-7pfc"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Gitea Git hosting","requires_auth":"low_privilege","summary":"An attacker can cause a denial of service by migrating a repository from a malicious server that reports a zero page size, exhausting server memory.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Gitea","cpe":[{"product":"gitea","vendor":"gitea"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-835","name":"Loop with Unreachable Exit Condition"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"When migrating a repository from another Gitea instance, Gitea used the page size reported in the source server's API settings to end its paginated downloads. A source that reported `max_response_items` as `0` made these loops run indefinitely and grow server memory until it was exhausted. Any user who can migrate repositories could point a migration at a server they control and cause a denial of service.","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 migration memory exhaustion from zero page size","id":"CVE-2026-104633","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"gitea:gitea","products":["gitea:gitea"],"type":"denial_of_service","year":"2026"},"n_packages":1,"n_references":5,"next":{"headline":"beam_mcp: JSON boolean and null tool arguments reach dispatch as strings","id":"CVE-2026-104634"},"packages":[{"ecosystem":"Bitnami","fixed":["28.1.0"],"introduced":["0"],"last_affected":[],"package":"gitea","purl":"pkg:bitnami/gitea","source":"BIT-gitea-2026-104633"}],"prev":{"headline":"Gitea fork workflow approval bypass through cancel and rerun","id":"CVE-2026-104632"},"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":"An attacker can cause a denial of service by migrating a repository from a malicious server that reports a zero page size, exhausting server memory.","url":"https://insights.sbomify.com/CVE-2026-104633/"}