{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-119441 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-119441 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-119441 is a high-severity vulnerability in Gitea, published on 1 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-119441 and fix it if it is affected.\n\nWhat it is: CVE-2026-119441 is a high-severity vulnerability in Gitea, published on 1 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-119441 in the wild and no public exploit code.\n\nAffected product: Gitea. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-119441/ (Markdown: https://insights.sbomify.com/CVE-2026-119441/index.md)","id":"CVE-2026-119441","markdown":"https://insights.sbomify.com/CVE-2026-119441/index.md","name":"CVE-2026-119441","record":{"aliases":["GHSA-jh8p-x4ch-389q"],"analysis":null,"analysis_generated_by":null,"assigner":"Gitea","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"`DELETE /api/v1/orgs/{org}/repos` deletes all repositories of an organization, but it did not enforce the public-only restriction of access tokens: the route only checked that the organization itself was public. A public-only token of an owner of a public organization could therefore permanently delete the organization's private repositories, which such a token must not reach. Routes that require organization ownership now reject public-only tokens.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Gitea public-only token bypass on bulk organization repository deletion","id":"CVE-2026-119441","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Session fixation in the CLI login flow allows an unauthenticated attacker to obtain a user's API token","id":"CVE-2026-119446"},"nickname":null,"packages":[],"prev":{"headline":"Decompression bomb in ezstd:decompress_using_ddict/2 allows BEAM memory exhaustion via unbounded output buffer","id":"CVE-2026-119434"},"products":["Gitea"],"published":"2026-11-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"partial"},"state":"PUBLISHED","updated":"2026-11-06","vendors":["Gitea"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-119441/"}