CVE-2026-110311
validatedZero produced an exploit or a check.GHSA-8j56-f865-gqq2 ↗EUVD-2026-103989 ↗
description
Gitea's API may expose metadata for attachments that are not associated with a release when a user creates a draft release. An authenticated user able to create draft releases can learn attachment names, identifiers, timestamps, sizes, and download counts for inaccessible repositories or unassociated uploads.
mitigation
Restrict draft-release creation and API access to trusted users until an upstream-fixed Gitea release is identified and deployed. Monitor draft-release API activity for unexpected use.
fixed in 28.2.0
outcome
Check only, differential: the check fires on the vulnerable build and is silent on the patched one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-18 18:57Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-110311
{ "etk_id": "ETK-2026-2197", "cve_id": "CVE-2026-110311", "display_id": "CVE-2026-110311", "ghsa_id": "GHSA-8j56-f865-gqq2", "euvd_id": "EUVD-2026-103989", "status": "published", "anchor_state": "anchored", "title": "Attachment metadata exposure in Gitea draft release API", "summary": "Gitea's API may expose metadata for attachments that are not associated with a release when a user creates a draft release. An authenticated user able to create draft releases can learn attachment names, identifiers, timestamps, sizes, and download counts for inaccessible repositories or unassociated uploads.", "mitigation": "Restrict draft-release creation and API access to trusted users until an upstream-fixed Gitea release is identified and deployed. Monitor draft-release API activity for unexpected use.", "vendor": "Gitea", "product": "Gitea", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 1.22.0, <= 28.1.0" ], "ecosystem": "go", "fixed_versions": [ "28.2.0" ], "package_name": "gitea.dev", "purl": "pkg:golang/gitea.dev" } ], "cwes": [ 200 ], "cvss_score": 4.3, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N", "epss_score": 0.0022, "epss_percentile": 0.1148, "epss_asof": "2026-10-20", "automation": "deterministic", "check": true, "check_confidence_basis": "differential", "exploit": false, "pipeline_minutes": 14.527050383333334, "t0_at": "2026-10-18T18:57:14.140000+00:00", "signals": { "check": { "at": "2026-10-20T17:42:37.996011+00:00", "days": 1.9481927779050927, "is_lower_bound": false, "measured_at": "2026-10-18T18:57:14.140000+00:00", "url": null }, "trigger_signal": { "at": "2026-10-18T18:57:14.140000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-18T18:57:14.140000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-110311" } } }
published 2026-10-20 17:28Z
last change 2026-10-21 02:54Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.