Live › vulnerability › CVE-2026-118762
A GitHub Actions workflow in the Monkeytype repository runs fork-controlled code with a write-scoped GITHUB_TOKEN when a pull request gets the format label. An outside contributor can use that to run code, read the token, and push changes or edit pull requests and issues in the repository.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 17:26 UTC. All times on this page are UTC.
This affects the Monkeytype repository's own CI workflow, not the Monkeytype application or user data. Teams that run or fork the Monkeytype repository and rely on that workflow are the ones to look at; teams that only use the hosted typing test are not exposed by this issue according to the sources.
No product ranges from the sources yet.
.github/workflows/fix-formatting.yml in the repository and check whether it uses pull_request_target.26.43.0; versions below it are affected per the sources.26.43.0 or later, per the sources.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Monkeytype is a minimalistic and customizable typing test. Prior to 26.43.0, the .github/workflows/fix-formatting.yml workflow runs on pull_request_target with repository write permissions, checks out a fork pull request, installs dependencies from the fork's package.json, and invokes the fork-controlled oxfmt binary. Because actions/checkout persists the elevated GITHUB_TOKEN in Git configuration until after untrusted code executes, an external contributor whose pull request receives the format label can run arbitrary code, read or exfiltrate the token, and push repository content or modify pull requests and issues. The issue affects the repository CI workflow, not the Monkeytype application or user data. This issue is fixed in version 26.43.0.
This page as .md · .json · in your agent: get_signal("CVE-2026-118762")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.