CVE-2026-110494 Gitea CVE debrief

Who should care

Gitea administrators and users with write access to releases should assess exposure and apply patches. Defenders should prioritize verifying exposure and applying patches for Gitea instances with untrusted users having write access to releases. This includes reviewing user access controls, applying patches, and monitoring for suspicious activity.

Why it matters

Defenders should care about CVE-2026-110494 as it allows users with write access to releases to re-link issue attachments, potentially exposing file metadata and requiring verification and patching to prevent unauthorized actions.

• Potential exposure of sensitive file metadata
• Possible unauthorized file renaming or deletion
• Required verification of Gitea instance exposure
• Necessity for timely patch application

Technical summary

The vulnerability allows users with write access to releases to re-link issue attachments, potentially exposing file names, sizes, and download counts. This issue affects Gitea versions up to 28.1.0. The vulnerability can be exploited by users with write access to releases who know the UUID of an attachment in that repository. This could lead to unauthorized exposure of sensitive file metadata and potential misuse of the attachment. The issue was addressed in Gitea version 28.2.0, which includes a patch to prevent unauthorized re-linking of issue attachments.

Defensive priority

Defenders should prioritize verifying exposure and applying patches for Gitea instances with untrusted users having write access to releases.

Recommended defensive actions

• Verify Gitea instance exposure and user access controls
• Apply patches from Gitea versions 28.2.0 or later
• Monitor for suspicious activity on Gitea releases and issue attachments
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, while vendor advisories and patches offer remediation guidance. The vulnerability was reported to the Gitea project, and a patch was developed and released in version 28.2.0. Users with write access to releases can re-link issue attachments, potentially exposing file metadata. Defenders should verify their Gitea instance exposure and apply patches from Gitea versions 28.2.0 or later.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.