ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-105268

Gitea issue attachment API allows changing comment attachments

Published Oct 14, 2026 · catalog updated Oct 14, 2026 · Gitea issue attachment API

Check if you run it

No confirmed exploitation is on record for CVE-2026-105268. EPSS is 0.20%. Act only if a listed version of Gitea issue attachment API is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Gitea issue attachment API).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.20%
Remediation
Advisory link
Affected products
Bitnami gitea

The Gitea API routes for issue attachments ( ) also accepted attachments that belong to comments on the issue. Because the author of an issue may edit and delete the issue's attachments, a user who opened an issue could rename or delete attachments that other users had posted in comments on that issue. The contents of the attachments could not be changed.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Bitnami gitea0 → 28.1.0

How to fix CVE-2026-105268

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-105268. EPSS is 0.20%. Act only if a listed version of Gitea issue attachment API is installed.

Which versions are affected?

Compare what you have installed with 0 → 28.1.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.20%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 14, 2026 · GitHub Advisory Database

    Detected

    The Gitea API routes for issue attachments ( ) also accepted attachments that belong to comments on the issue. Because the author of an issue may edit and delete the issue's attachments, a user who opened an issue could rename or delete attachments that other users had posted in comments on that issue. The contents of the attachments could not be changed.

  2. Oct 14, 2026 · GitHub Advisory Database

    Fix available

    gitea fixed in 28.1.0

  3. Oct 14, 2026 · GitHub Advisory Database

    Fix available

    gitea fixed in 28.1.0

  4. Oct 14, 2026 · GitHub Advisory Database

    Updated

    The Gitea API routes for issue attachments ( ) also accepted attachments that belong to comments on the issue. Because the author of an issue may edit and delete the issue's attachments, a user who opened an issue could rename or delete attachments that other users had posted in comments on that issue. The contents of the attachments could not be changed.

Sources

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.