{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-119533 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-119533 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-119533 is a high-severity vulnerability in Gitea, published on 1 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-119533 and fix it if it is affected.\n\nWhat it is: CVE-2026-119533 is a high-severity vulnerability in Gitea, published on 1 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-119533 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-119533/ (Markdown: https://insights.sbomify.com/CVE-2026-119533/index.md)","id":"CVE-2026-119533","markdown":"https://insights.sbomify.com/CVE-2026-119533/index.md","name":"CVE-2026-119533","record":{"aliases":["GHSA-c45m-jm46-mwxg"],"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:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Repository and organization project boards listed the pull requests that reference each issue on the board without checking whether the viewer can read them. When a private pull request mentions an issue on a board the viewer can open, the board revealed the private repository's path and the pull request's number, title and state, to anonymous visitors in the case of a public board. The pull request body, diff and files were not exposed. Boards now skip linked pull requests in repositories where the viewer cannot read pull requests.","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 private pull request disclosure on project boards","id":"CVE-2026-119533","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Org.infinispan/infinispan-query: infinispan: deeply nested ickle queries can trigger a stackoverflowerror","id":"CVE-2026-119542"},"nickname":null,"packages":[],"prev":{"headline":"Live Composer \u003c 2.1.24 - Contributor+ Stored XSS via Module Area Shortcode","id":"CVE-2026-119531"},"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-119533/"}