Skip to main content
VulnerabilityPublished

CVE-2026-94563: nukeviet · Path Traversal

Affects nukevietSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.0 Medium : upgrade to 4.6.01 when convenient.

Data as of 20 Nov 2026, 19:14 UTC

CVSS 3.1 base score
6.0Medium
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.16.0
Patch
Available – fixed in 4.6.01
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:L

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 20 Nov 2026.

What to do

Upgrade nukeviet and nukeviet/nukeviet to 4.6.01.

Affected software

ProductAffectedFixed in
nukevietnukevietAffected
  • >=4.5.00 <4.6.01
Fixed in
  • 4.6.01
GitHubnukeviet/nukevietpkg:github/nukeviet/nukevietOther threatsAffected
  • >=4.5.00 <4.6.01
Fixed in
  • 4.6.01

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

AI-suggested

Upgrade NukeViet CMS to version 4.6.01 or later, where this vulnerability is fixed. No other mitigations are indicated or required as the fix addresses the root cause.

Description

NukeViet CMS versions from 4.5.00 up to but not including 4.6.01 contain a path traversal vulnerability in the smimeadd handler of the settings module. An authenticated administrator can upload a PKCS#12 S/MIME certificate with an X.509 Subject CN containing path traversal sequences, allowing overwriting of certificate files outside the intended directory. This can lead to overwriting critical assets such as DKIM private keys and, if curl.cainfo is empty, the cacert.pem file, potentially undermining TLS verification. The issue is fixed in version 4.6.01.

References

Community reviews

Loading reviews…