{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-119625 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-119625 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-119625 is a medium-severity vulnerability in Gitea, published on 1 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-119625 and fix it if it is affected.\n\nWhat it is: CVE-2026-119625 is a medium-severity vulnerability in Gitea, published on 1 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-119625 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-119625/ (Markdown: https://insights.sbomify.com/CVE-2026-119625/index.md)","id":"CVE-2026-119625","markdown":"https://insights.sbomify.com/CVE-2026-119625/index.md","name":"CVE-2026-119625","record":{"aliases":["GHSA-3fv3-hhmm-4x2q"],"analysis":null,"analysis_generated_by":null,"assigner":"Gitea","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"The `/{username}` web route accepted personal access tokens over HTTP Basic authentication without checking their scope. A token confined to an unrelated scope, such as `read:issue`, could read its owner's private activity through the user RSS/Atom feed and the profile activity tab, and other members' activity in a private organization through the organization feed; a public-only token could list the owner's private repositories and organizations and render private profile READMEs. For a site administrator's token this applied to every account. Tokens are now accepted on this route only for feeds, which require `read:user` or `read:organization`.","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 user and organization feed token scope bypass","id":"CVE-2026-119625","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Gitea limited-visibility profile disclosure with public-only tokens","id":"CVE-2026-119627"},"nickname":null,"packages":[],"prev":{"headline":"37954679 cak-filemanagement-system add_logs.php move_uploaded_file unrestricted upload","id":"CVE-2026-119620"},"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-11-06","vendors":["Gitea"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-119625/"}