XML Injection Affecting logto-1.39 package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.61% (47th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-LOGTO139-19656847
  • published10 Sept 2026
  • disclosed1 Sept 2026

Introduced: 1 Sep 2026

CVE-2026-83608  (opens in a new tab)
CWE-91  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest logto-1.39.

NVD Description

Note: Versions mentioned in the description apply only to the upstream logto-1.39 package and not the logto-1.39 package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. Prior to @xmldom/xmldom versions 0.8.15 and 0.9.12, and in xmldom version 0.6.0 and earlier, the DOCUMENT_TYPE_NODE branch in lib/dom.js validates publicId, systemId, and internalSubset under requireWellFormed: true but emits DocumentType.name verbatim. A name containing > or whitespace can terminate the <!DOCTYPE ...> declaration and inject sibling markup; the value can be supplied through createDocumentType() on the 0.8.x and unscoped lines or through a direct DocumentType.name property write on every affected line. The default path and legacy creation-time behavior remain permissive, while the vulnerable strict path fails to enforce an XML Name. This issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fixed version is available for xmldom.

CVSS Base Scores

version 3.1