{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-119627 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-119627 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-119627 is a medium-severity vulnerability in Gitea, published on 1 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-119627 and fix it if it is affected.\n\nWhat it is: CVE-2026-119627 is a medium-severity vulnerability in Gitea, published on 1 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-119627 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-119627/ (Markdown: https://insights.sbomify.com/CVE-2026-119627/index.md)","id":"CVE-2026-119627","markdown":"https://insights.sbomify.com/CVE-2026-119627/index.md","name":"CVE-2026-119627","record":{"aliases":["GHSA-5j4v-rwqr-vpq7"],"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-1220","name":"Insufficient Granularity of Access Control"}],"description":"The web profile and RSS/Atom feed routes of users and organizations checked only whether a signed-in viewer could see a limited-visibility owner, without considering the `public-only` restriction of the personal access token used to authenticate. Any user holding a public-only token could send it over HTTP Basic authentication to read the profile and activity feed of limited-visibility users and organizations, which are hidden from anonymous visitors and refused on the equivalent API routes. The disclosure covers existence, profile metadata and public activity; it does not grant write access.","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 limited-visibility profile disclosure with public-only tokens","id":"CVE-2026-119627","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"Improper release of expired privileged access checkouts in the PAM scheduled check-in task in Devolutions Server 2025.3.2.0 through 2026.2.2","id":"CVE-2026-119636"},"nickname":null,"packages":[],"prev":{"headline":"Gitea user and organization feed token scope bypass","id":"CVE-2026-119625"},"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-119627/"}