Skip to main content
VulnerabilityPublished

CVE-2026-119291: zuke · Link Following

Affects zukeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.5 Medium : upgrade to 1.4.0 when convenient.

Data as of 30 Oct 2026, 16:18 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.5
Patch
Available – fixed in 1.4.0
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 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 30 Oct 2026.

What to do

Upgrade zuke and zuke-build/zuke to 1.4.0.

Affected software

ProductAffectedFixed in
zuke-buildzukeAffected
  • <1.4.0
Fixed in
  • 1.4.0
GitHubzuke-build/zukepkg:github/zuke-build/zukeOther threatsAffected
  • <1.4.0
Fixed in
  • 1.4.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to zuke version 1.4.0 or later, where this vulnerability is fixed. No other mitigation is required as the fix addresses the symbolic link handling issue.

Description

CVE-2026-119291 is a vulnerability in zuke-build's zuke automation system prior to version 1.4.0. It involves improper handling of symbolic links during setup and import operations, allowing an attacker to supply a malicious repository or template with symbolic links that cause files outside the intended directory to be overwritten with the user's permissions. This can lead to unauthorized modification of files. The issue is fixed in version 1.4.0.

References

Community reviews

Loading reviews…