CVE-2026-118386

The record

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.

Affected packages

Related vulnerabilities

• CVE-2026-116667 Tanium addressed an improper access controls vulnerability in Discover. CWE-863
• CVE-2026-116661 Tanium addressed an improper access controls vulnerability in Enforce. CWE-863
• CVE-2026-116664 Tanium addressed an improper access controls vulnerability in Discover. CWE-863
• CVE-2026-121541 In Docker Buildx versions v0.19.0 through v0.38.0, an untrusted Bake definition that… CWE-863
• CVE-2026-120930 Incorrect authorization in Blink in Google Chrome prior to 156.0.8078.47 allowed a remote… CWE-863
• CVE-2026-95860 node-opcua is an OPC UA implementation for TypeScript and Node.js. CWE-863
• CVE-2026-121255 Incorrect authorization in Autofill AI in Google Chrome prior to 157.0.8103.38 allowed a… CWE-863
• CVE-2026-121248 Incorrect authorization in API in Google Chrome prior to 157.0.8103.38 allowed a remote… CWE-863