Skip to main content
VulnerabilityPublished Updated

CVE-2026-76796: Newell Brands DYMO Connect Desktop · External Control of File Name or Path

Affects Newell Brands DYMO Connect DesktopSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.0 Medium · fixed in 1.6.2 : update Newell Brands DYMO Connect Desktop when convenient.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 3.1 base score
4.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.6.2
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Sep 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

Affected software

ProductAffectedFixed in
Newell BrandsDYMO Connect DesktopAffected
  • <1.6.2
Fixed in–

AI-suggested

Upgrade DYMO Connect Desktop to version 1.6.2 or later, where the vulnerability is fixed by restricting file access based on file extension. Note that arbitrary-location reads of files with allowed image extensions remain possible by design and are considered an accepted residual risk.

Description

The LoadImageAsPngBase64 endpoint of the Newell Brands DYMO Connect Desktop local web service accepts a file path parameter without adequate validation, allowing a crafted path to read arbitrary image files from the host filesystem outside the intended scope. Fixed in 1.6.2. The fix limits access by file extension only, not by directory - arbitrary-location reads of files with an allowed image extension remain possible by design (accepted residual risk).

References

Community reviews

Loading reviews…