CVE-2026-129840 json
GitHub Actions pull_request_target code injection in nrfconnect/ncs-zigbee (build_documentation.yml)
published yesterday modified yesterday also EUVD-2026-131246
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 62%
- public exploits
- 0
- none known
Summary
In the nrfconnect/ncs-zigbee repository, the GitHub Actions workflow .github/workflows/build_documentation.yml used the pull_request_target trigger while checking out and executing untrusted pull request code. This allowed a pull request from a fork to run attacker-controlled code in the base repository context with a write-scoped GITHUB_TOKEN (contents: write, pages: write, pull-requests: write), enabling remote code execution in CI, token exfiltration, and unauthorized modification of repository content and GitHub Pages. The workflow was disabled and then rewritten to remove the issue.
Patch / fix
- github.com/nrfconnect/ncs-zigbee@163246b commit
- github.com/nrfconnect/ncs-zigbee#76 pull request
Is CVE-2026-129840 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.96% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-21).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected products
-
Nordic Semiconductor ASA ncs-zigbee (nRF Connect SDK Zigbee R23 add-on, GitHub repository nrfconnect/ncs-zigbee)
- main branch from commit 163246b7be03c4ad2e88860a437ca827810d73cc (2026-01-15) until the fix in pull request #76 (2026-01-21)
Classification
- Weakness
-
- CWE-829 Inclusion of Functionality from Untrusted Control Sphere
References
Sources
- CVE List CVE-2026-129840
- NVD CVE-2026-129840
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.