# CVE-2026-118762: Monkeytype: fork PR can execute code with elevated GITHUB_TOKEN


- **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-47v3-j88w-92f8

## What is CVE-2026-118762?

CVE-2026-118762 is a critical vulnerability in monkeytypegame monkeytype, published on 29 Oct 2026. 

### Official description

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.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

## Which versions are affected by CVE-2026-118762?


## How do I fix CVE-2026-118762?

No fix has been published for CVE-2026-118762 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-118762 being exploited?

There is no known exploitation of CVE-2026-118762 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-118762 and fix it if it is affected.

What it is: CVE-2026-118762 is a critical vulnerability in monkeytypegame monkeytype, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118762 in the wild and no public exploit code.

Affected product: monkeytypegame monkeytype. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-118762/ (Markdown: https://insights.sbomify.com/CVE-2026-118762/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-118762
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-118762
- OSV: https://osv.dev/vulnerability/CVE-2026-118762

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-118762/
Summaries are generated and may contain mistakes; the official description above is the record.