Description
Unhead is a document head and template manager. Prior to 2.1.13, useHeadSafe() is the composable that Nuxt's own documentation explicitly recommends for rendering user-supplied content in <head> safely. Internally, the hasDangerousProtocol() function in packages/unhead/src/plugins/safe.ts decodes HTML entities before checking for blocked URI schemes (javascript:, data:, vbscript:). The decoder uses two regular expressions with fixed-width digit caps. The HTML5 specification imposes no limit on leading zeros in numeric character references. When a padded entity exceeds the regex digit cap, the decoder silently skips it. The undecoded string is then passed to startsWith('javascript:'), which does not match. makeTagSafe() writes the raw value directly into SSR HTML output. The browser's HTML parser decodes the padded entity natively and constructs the blocked URI. This vulnerability is fixed in 2.1.13.
Affected products
unjs: unhead
References4
- github.com/unjs/unhead/security/advisories/GHSA-95h2-gj7x-gx9w ExploitMitigationVendor Advisory
- github.com/unjs/unhead/security/advisories/GHSA-95h2-gj7x-gx9w ExploitMitigationVendor Advisory
- github.com/unjs/unhead/commit/961ea781e091853812ffe17f8cda17105… Patch
- github.com/unjs/unhead/releases/tag/v2.1.13 ProductRelease Notes
Metrics
- CVSS 3.1
-
6.1
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N - EPSS — exploit probability
- 0% percentile: 23 · as of 12 November 2026
- CWE
- CWE-184
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.