check-spelling workflow vulnerable to GITHUB_TOKEN leakage via symlink attack
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-532.
Summary
check-spelling is a github action which provides CI spell checking. In affected versions and for a repository with the [check-spelling action](https://github.com/marketplace/actions/check-spelling) enabled that triggers on `pull_request_target` (or `schedule`), an attacker can send a crafted Pull Request that causes a `GITHUB_TOKEN` to be exposed. With the `GITHUB_TOKEN`, it's possible to push commits to the repository bypassing standard approval processes. Commits to the repository could then steal any/all secrets available to the repository. As a workaround users may can either: [Disable the workflow](https://docs.github.com/en/actions/managing-workflow-runs/disabling-and-enabling-a-workflow) until you've fixed all branches or Set repository to [Allow specific actions](https://docs.github.com/en/github/administering-a-repository/managing-repository-settings/disabling-or-limiting-github-actions-for-a-repository#allowing-specific-actions-to-run). check-spelling isn't a verified creator and it certainly won't be anytime soon. You could then explicitly add other actions that your repository uses. Set repository [Workflow permissions](https://docs.github.com/en/github/administering-a-repository/managing-repository-settings/disabling-or-limiting-github-actions-for-a-repository#setting-the-permissions-of-the-github_token-for-your-repository) to `Read repository contents permission`. Workflows using `check-spelling/check-spelling@main` will get the fix automatically. Workflows using a pinned sha or tagged version will need to change the affected workflows for all repository branches to the latest version. Users can verify who and which Pull Requests have been running the action by looking up the spelling.yml action in the Actions tab of their repositories, e.g., https://github.com/check-spelling/check-spelling/actions/workflows/spelling.yml - you can filter PRs by adding ?query=event%3Apull_request_target, e.g., https://github.com/check-spelling/check-spelling/actions/workflows/spelling.yml?query=event%3Apull_request_target.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| check-spelling | check-spelling | before 0.0.19 | 0.0.19 | Patch available | CNA |
| — | check-spelling/check-spelling (GitHub Actions) | before 0.0.19 | 0.0.19 | Patch available | GHSA-g86g-chm8-7r2p |
- check-spelling Vendorcheck-spelling Affected before 0.0.19 Fixed in 0.0.19 Patch available CNA
- check-spelling/check-spelling (GitHub Actions) Vendor— Affected before 0.0.19 Fixed in 0.0.19 Patch available GHSA-g86g-chm8-7r2p
CPE configurations NVD · 1
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:check-spelling:check-spelling:*:*:*:*:*:*:*:* | before 0.0.19 | Vulnerable | check-spelling |
- cpe:2.3:a:check-spelling:check-spelling:*:*:*:*:*:*:*:* Versions before 0.0.19 Vulnerable ·check-spelling
Remediation
- Fix · CNA check-spelling (check-spelling) Fixed in 0.0.19
- Fix · GHSA-g86g-chm8-7r2p check-spelling/check-spelling (GitHub Actions) Fixed in 0.0.19 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2021-32724
- 2026-10-03 Alias added: GHSA-g86g-chm8-7r2p
References
Patch 1
Advisory 2
Sources
- CVE-2021-32724 · CVE Program
- CVE-2021-32724 · NVD
- FIRST EPSS
- GHSA-g86g-chm8-7r2p · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences