CVE-2026-105964
validatedZero produced an exploit or a check.GHSA-6f9g-7jgm-m5ph ↗EUVD-2026-103985 ↗
description
Gitea Actions artifact v4 handlers can accept artifact-service requests without an effective body-size limit. An attacker able to run a workflow and obtain its runner token could exhaust server memory and cause the Gitea process to stop.
mitigation
Enforce a 1 MiB request-body limit for the Gitea Actions artifact service, including at a reverse proxy if necessary. Restrict workflow execution to trusted users and protect or rotate runner tokens.
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:56Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-105964
{ "etk_id": "ETK-2026-2002", "cve_id": "CVE-2026-105964", "display_id": "CVE-2026-105964", "ghsa_id": "GHSA-6f9g-7jgm-m5ph", "euvd_id": "EUVD-2026-103985", "status": "published", "anchor_state": "anchored", "title": "Unbounded request body handling in Gitea Actions artifacts", "summary": "Gitea Actions artifact v4 handlers can accept artifact-service requests without an effective body-size limit. An attacker able to run a workflow and obtain its runner token could exhaust server memory and cause the Gitea process to stop.", "mitigation": "Enforce a 1 MiB request-body limit for the Gitea Actions artifact service, including at a reverse proxy if necessary. Restrict workflow execution to trusted users and protect or rotate runner tokens.", "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": [ 770 ], "cvss_score": 6.5, "cvss_src": "nvd", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", "epss_score": 0.0031, "epss_percentile": 0.2189, "epss_asof": "2026-10-20", "automation": "deterministic", "check": true, "check_confidence_basis": "differential", "exploit": false, "pipeline_minutes": 40.93366915, "t0_at": "2026-10-18T18:56:47.881000+00:00", "signals": { "check": { "at": "2026-10-18T19:52:58.089187+00:00", "days": 0.03900703920138889, "is_lower_bound": false, "measured_at": "2026-10-18T18:56:47.881000+00:00", "url": null }, "trigger_signal": { "at": "2026-10-18T18:56:47.881000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-18T18:56:47.881000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-105964" } } }
published 2026-10-18 19:11Z
last change 2026-10-21 18:33Z
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.