The goldmark HTML renderer (versions before 1.7.17) contains a cross-site scripting vulnerability stemming from improper validation ordering. The flaw allows attackers to bypass protocol filtering through HTML entity encoding, enabling execution of arbitrary JavaScript in applications using affected versions of the github.com/yuin/goldmark/renderer/html package. This impacts any system that renders markdown content with this library without proper input sanitization. The vulnerability presents a network-exploitable attack requiring no privileges and minimal complexity, though user interaction is necessary for exploitation. The CVSS 3.1 score of 6.1 (Medium) reflects low confidentiality and integrity impacts with no availability impact. The EPSS score of 0.0004 suggests minimal active exploitation likelihood relative to the broader CVE landscape. Currently, this vulnerability shows no signs of active exploitation in the wild and does not appear on the CISA Known Exploited Vulnerabilities catalog. Community attention remains limited, as indicated by the moderate FAUCET risk score of 43.0/100. Organizations should prioritize patching to version 1.7.17 or later, particularly for internet-facing applications that process untrusted markdown content.
| Vendor | Product | Version(s) | CPE |
|---|---|---|---|
< 1.7.17CPE matchmatch criteria | cpe:2.3:a:yuin:goldmark:*:*:*:*:*:*:*:* |
CVSS version used by this source: 4.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
The average CVE in this peer group has 0.0 Twitter, 0.0 Reddit, 0.1 Bluesky, 0.0 Mastodon, and 0.1 GitHub mentions.
No media coverage found for this CVE.
The average CVE in this peer group has 0.1 InfoSec Media, 0.0 Vendor Blog, and 0.0 Security Researcher mentions.
goldmark vulnerable to Cross-site Scripting (XSS)
Apr 17, 2026Versions of the package github.com/yuin/goldmark/renderer/html before 1.7.17 are vulnerable to Cross-site Scripting (XSS) due to improper ordering of URL validation and normalization. The renderer validates link destinations using a prefix-based check (IsDangerousURL) before resolving HTML entities. This allows an attacker to bypass protocol filtering by encoding dangerous schemes using HTML5 named character references. For example, a payload such as javascript:alert(1) is not recognized as dangerous during validation, leading to arbitrary script execution in the context of applications that render the URL.
Apr 14, 2026