Runner code execution via permanent approval trust
Published Jul 3, 2026 · Updated Jul 3, 2026
Improper authorization in Gitea Actions 1.20.0 through 1.26.2 allows remote authenticated users to execute workflows on CI runners. The ifNeedApproval function treats any earlier approved action_run for the same repository and trigger user as permanent trust, without binding approval to a pull request, commit, or workflow. Exploitation requires a fork-capable account and one administrator approval of a benign run; later malicious workflow YAML executes without further approval.
Summary
What happened
Improper authorization in Gitea Actions 1.20.0 through 1.26.2 allows remote authenticated users to execute workflows on CI runners. The ifNeedApproval function treats any earlier approved action_run for the same repository and trigger user as permanent trust, without binding approval to a pull request, commit, or workflow. Exploitation requires a fork-capable account and one administrator approval of a benign run; later malicious workflow YAML executes without further approval.
The record
- CVE
- CVE-2026-58424
- Published
- Jul 3, 2026
- Updated
- Jul 3, 2026
- Vendor
- Gitea
- Product
- Gitea
- Classifications
- CWE-285, CWE-732, CWE-863, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 3, 2026CVE publishedPublication date reported by the CVE source.
- Jul 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.26.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-777r-4v59-6486 manual reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo