CVE-2026-118386
No CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
Workflows triggered by a pull request review were read from the commit named in the review's `commit_id`, while the fork restrictions were decided by the reviewed pull request, and the commit was not checked to belong to that pull request. A user with read access to a repository could place a commit of their own in it, through a fork pull request or an AGit push, and submit a review naming that commit on a pull request whose head branch is in the same repository. On instances with a runner serving the repository, the attacker's workflow then ran without approval, received the Actions secrets of the repository and its owner, and got a `GITEA_TOKEN` with write access to the repository. Review-triggered workflows now run on the pull request head.
- EPSS
- 0.2% estimated probability of exploitation activity in the next 30 days; 10th percentile. Scored 2026-11-01. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-863 Incorrect Authorization
- Published
- Modified
- Record from
- the NVD, synced
Ask an AI about this CVE
ChatGPTClaudePerplexityGoogle AI Mode
Show the prompt
Explain CVE-2026-118386 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-118386?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-118386?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an estimate of exploitation activity across the internet over the next 30 days, not a prediction for my systems). Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.