Skip to main content
Menu
CVEs

Nordic Semiconductor ncs-zigbee code injection in GitHub Actions documentation workflow

CVE-2026-129840EUVD-2026-131246GHSA-4866-QGPH-QJMXPublished November 20, 2026, updated

7.5HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

The ncs-zigbee repository from Nordic Semiconductor ASA has a GitHub Actions workflow (build_documentation.yml) that ran untrusted pull request code with write-level access. An attacker can remotely, without logging in, submit a pull request from a fork to run their own code in the repository's CI, steal its access token, and modify repository content and GitHub Pages.

Written by a model

Original description

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.

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129840 (GitHub Actions pull_request_target code injection in nrfconnect/ncs-zigbee (build_documentation.yml)), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129840 (entry last updated 2026-11-20):
Affected:
- Nordic Semiconductor ASA ncs-zigbee (nRF Connect SDK Zigbee R23 add-on, GitHub repository nrfconnect/ncs-zigbee): versions main branch from commit 163246b7be03c4ad2e88860a437ca827810d73cc (2026-01-15) until the fix in pull request #76 (2026-01-21)
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129840 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129840 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nrfconnect/ncs-zigbee/pull/76
- https://github.com/nrfconnect/ncs-zigbee/commit/163246b7be03c4ad2e88860a437ca827810d73cc
- https://securitylab.github.com/resources/github-actions-preventing-pwn-requests/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129840
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129840"}.

Affected versions

cve.now Index

33Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.5/10CVSS 7.5
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 78 if added to CISA KEV
  • Would score about 73 if CISA's SSVC rates exploitation active
  • Would score about 38 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Evidence 5

Questions about CVE-2026-129840

Is CVE-2026-129840 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-129840?

ncs-zigbee (nRF Connect SDK Zigbee R23 add-on, GitHub repository nrfconnect/ncs-zigbee): version main branch from commit 163246b7be03c4ad2e88860a437ca827810d73cc (2026-01-15) until the fix in pull request #76 (2026-01-21).

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.