XXE (XML External Entity) in Newell Brands DYMO ID (CVE-2026-101893)
Summary
Vulnerability in Newell Brands DYMO ID (CVE-2026-101893). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.6.0 or later.
Original description
The description as published by the source.
Newell Brands DYMO ID 1.5.1.71 parses job files using XmlDocument.Load() without disabling DTD processing. The PC Job Files view automatically parses every recognized job file extension on folder browse. A crafted file on any browsed network share can perform SSRF, capture NTLMv2 credentials, read local files, or crash the process. Fixed in 1.6.0.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-101893 has been found in Newell Brands DYMO ID.
Risk of unauthorized operations or information disclosure. CVSS score: 4.4/10.
What to do: upgrade Newell Brands DYMO ID to 1.6.0 or later.
If unsure, ask your IT team or search "Newell Brands DYMO ID CVE-2026-101893" on the vendor's site.
CVE-2026-101893 (Newell Brands DYMO ID) — CWE-611 / CVSS v3 4.4
Attack vector: local / no user interaction
Patched: 1.6.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-611) exists in Newell Brands DYMO ID.
Check the vendor advisory for the affected versions of Newell Brands DYMO ID.
Severity: Medium (CVSS 4.4/10). Risk of unauthorized operations or information disclosure.
Update to 1.6.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Newell Brands DYMO ID を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Newell Brands DYMO ID to 1.6.0ステージング環境で 1.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web mediaserver.newellrubbermaid.com
- web raw.githubusercontent.com
- web cve.org
- web dymo.com
- web nvd.nist.gov
- web github.com