What is CVE-2026-58426?
Gitea Actions Artifacts V4 signed URL HMAC ambiguity allows cross-repository artifact read and cross-task upload-state write
The record classifies CVE-2026-58426 under weakness class CWE-347. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction, and has high impact on confidentiality, integrity. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 109 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 9.6 — CRITICAL
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N - EPSS (FIRST)
- 0.3% probability of exploitation in the next 30 days, higher than 21.0% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 7.6/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-07-03, last modified 2026-07-06
Is CVE-2026-58426 being exploited?
Weaponised exploit code for CVE-2026-58426 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 23 in the Threadlinqs vulnerability feed.
- trickest/cve (trickest)
Affected products and versions
- Gitea: Open Source Git Server
Affected software packages:
go:code.gitea.io/gitea— patched in 1.26.2
How to fix CVE-2026-58426
Fixed versions are recorded for 1 package: go:code.gitea.io/gitea 1.26.2. No vendor patch reference has been recorded for CVE-2026-58426 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-58426
1 tracked threat in the Threadlinqs corpus references CVE-2026-58426, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories, public proof-of-concept repositories. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.