Skip to main content
CVE-2026-129840VulnerabilityPublished

In the nrfconnect/ncs-zigbee repository, the GitHub Actions workflow .github/workflows/build_documentation.yml used

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-129840· High 7.5

Not known to be exploited · CVSS 7.5 High.

Data as of 20 Nov 2026, 10:34 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (YesWeHack)CVSS 3.17.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Nordic Semiconductor ASAncs-zigbee (nRF Connect SDK Zigbee R23 add-on, GitHub repository nrfconnect/ncs-zigbee)Affected
  • =main branch from commit 163246b7be03c4ad2e88860a437ca827810d73cc (2026-01-15) until the fix in pull request #76 (2026-01-21)
Fixed in–

AI-suggested

The vulnerable workflow was disabled and rewritten to remove the use of the pull_request_target trigger with untrusted code execution. Users should ensure that workflows do not execute untrusted pull request code with elevated permissions. Since the issue has been addressed by disabling and rewriting the workflow, no further immediate action is required.

Description

A GitHub Actions workflow in the nrfconnect/ncs-zigbee repository used the pull_request_target trigger to check out and execute untrusted pull request code. This allowed attackers submitting pull requests from forks to run code with write-scoped GITHUB_TOKEN permissions, enabling remote code execution in the CI environment, token exfiltration, and unauthorized repository modifications. The vulnerable workflow was disabled and rewritten to remove the issue.

References

Community reviews

Loading reviews…