Skip to main content
Menu
CVEs

CVE

Gitea file deletion via path traversal in release edit

CVE-2026-123065EUVD-2026-126123

Exploited
No known exploitation
Fix
Fixed in 28.4.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 28.4.0.

Published
Last modified
Reference
Last checked
0.24% · 15th percentile
0/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

Gitea versions before the fix let a user with write access to releases delete files belonging to other attachments, which broke downloads of the affected issue, comment or release file. The attacker needs the target attachment's UUID, and the attachment record itself remains in place.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

When a release was edited, the files of the attachments to remove were deleted by the identifiers submitted in the form rather than by the attachments verified to belong to the release. A user with write access to the releases of any repository, including their own, could submit a crafted identifier that resolves to the stored file of another attachment and delete it, provided they know that attachment's UUID. The attachment record stayed, so downloads of the affected issue, comment or release file failed. Release edits now only delete the files of attachments that belong to the release.

cve.now Index

0Pcve.now Index 0 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 55 if added to CISA KEV
  • Would score about 50 if CISA's SSVC rates exploitation active
  • Would score about 22 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 28.4.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-123065 (Gitea deletion of arbitrary attachment files through release edit), 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-123065 (entry last updated 2026-11-15):
Affected:
- Gitea Gitea: from 1.15.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-123065 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-123065 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-4p89-xcq8-xfhm
- https://github.com/go-gitea/gitea/pull/40120
- https://github.com/go-gitea/gitea/pull/40268
- 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-123065
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-123065"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • gitea.dev

    From 1.15.0 · fixed in 28.4.0

Evidence 7

Vendor advisory · 2

Establishes: Affected and fixed versions.

  1. Advisory
  2. Link

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 3

  1. Patch
  2. Patch
  3. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-123065

Is CVE-2026-123065 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: cve.now feed data

Which versions are affected by CVE-2026-123065?

gitea.dev: from 1.15.0 before 28.4.0.Source: cve.now feed data

How do I fix CVE-2026-123065?

Upgrade to a fixed version: 28.4.0.Source: cve.now feed data