# CVE-2026-127958: Gitea disclosure of pending pull request reviews created through the API

> Anyone reading a Gitea pull request can see pending API-created reviews and comments before the reviewer submits them.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 15 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-859w-9wv7-c5x9

## What is CVE-2026-127958?

CVE-2026-127958 is a medium-severity information disclosure vulnerability in Gitea, published on 15 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A pull request review created through the API as a draft (`event` set to `PENDING` or left empty) was added to the pull request timeline and announced through notifications and activity feeds like a submitted review. Its body and line comments were therefore visible to everyone who can read the pull request, including anonymous visitors of a public repository, before the reviewer submitted it. Pending reviews no longer get a timeline entry or notifications until they are submitted.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

An affected version is exposed as installed. No special setting or call is needed.


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

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

## Is CVE-2026-127958 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-127958 is a medium-severity information disclosure vulnerability in Gitea, published on 15 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-127958 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

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-127958/ (Markdown: https://insights.sbomify.com/CVE-2026-127958/index.md)
```

## Sources

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

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