# CVE-2026-119533: Gitea private pull request disclosure on project boards


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 1 Nov 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-c45m-jm46-mwxg

## What is CVE-2026-119533?

CVE-2026-119533 is a high-severity vulnerability in Gitea, published on 1 Nov 2026. 

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-119533?


## How do I fix CVE-2026-119533?

No fix has been published for CVE-2026-119533 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119533 being exploited?

There is no known exploitation of CVE-2026-119533 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119533 and fix it if it is affected.

What it is: CVE-2026-119533 is a high-severity vulnerability in Gitea, published on 1 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-119533 in the wild and no public exploit code.

Affected product: Gitea. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119533/ (Markdown: https://insights.sbomify.com/CVE-2026-119533/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119533
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119533
- OSV: https://osv.dev/vulnerability/CVE-2026-119533

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119533/
Summaries are generated and may contain mistakes; the official description above is the record.