{"items":[{"id":"NVI-00013800","kind":"vulnerability","title":"Cross-site scripting via  slot content in Nuxt's head components","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-m3q2-p4fw-w38m","CVE-2026-56317"],"plain_summary":"GitHub lists this reviewed advisory for nuxt, nuxt. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-694025c5499b02b079484d540ed2fd1c"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-06-24T19:17:13.783Z","value":"6.1 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-694025c5499b02b079484d540ed2fd1c"},{"kind":"CVSS","as_of":"2026-06-24T19:17:13.783Z","value":"2.3 LOW (4.0)","meaning":"disclosure@vulncheck.com severity; no combined Null risk score.","source_id":"sr-694025c5499b02b079484d540ed2fd1c"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-0674c86e679bccd5982e359bd87baa3b","url":"https://github.com/advisories/GHSA-m3q2-p4fw-w38m","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-m3q2-p4fw-w38m","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T22:54:12.705Z"},{"id":"sr-694025c5499b02b079484d540ed2fd1c","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-56317","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-56317","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-08T01:48:33.286Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0674c86e679bccd5982e359bd87baa3b"],"technology":"nuxt","known_exclusions":[],"conditions_summary":"### Impact\n\nNuxt's globally registered `` component (from `@unhead/vue` head components, re-exported by Nuxt) wrote its default-slot content to the `innerHTML` of the `` head tag, bypassing the HTML escaping that `{{ }}` interpolation normally applies in Vue templates.\n\nApplications that placed untrusted, attacker-controllable data inside a `` slot, for example:\n\n```vue\n{{ route.query.banner }}\n```\n\nwould emit that value unescaped inside `` in the server-rendered HTML. With scripting enabled, the HTML parser treats `` content in `` under the \"in head noscript\" insertion mode: any tag other than `link`, `meta`, `noframes`, or `style` implicitly closes `` and is re-processed in the head. A payload such as `...` therefore escapes the element and executes in the document context.\n\nSibling head components (``, ``) were not affected because they already routed slot text through the safe `textContent` path.\n\n### Affected versions\n\nAll currently supported versions of `nuxt` that ship the `` global component.\n\n### Patches\n\nFixed in `nuxt@4.4.7` (commit [`4b054e9d`]","public_affected_ranges":[">= 4.0.0, < 4.4.7"]},{"certainty":"source_listed","source_ids":["sr-0674c86e679bccd5982e359bd87baa3b"],"technology":"nuxt","known_exclusions":[],"conditions_summary":"### Impact\n\nNuxt's globally registered `` component (from `@unhead/vue` head components, re-exported by Nuxt) wrote its default-slot content to the `innerHTML` of the `` head tag, bypassing the HTML escaping that `{{ }}` interpolation normally applies in Vue templates.\n\nApplications that placed untrusted, attacker-controllable data inside a `` slot, for example:\n\n```vue\n{{ route.query.banner }}\n```\n\nwould emit that value unescaped inside `` in the server-rendered HTML. With scripting enabled, the HTML parser treats `` content in `` under the \"in head noscript\" insertion mode: any tag other than `link`, `meta`, `noframes`, or `style` implicitly closes `` and is re-processed in the head. A payload such as `...` therefore escapes the element and executes in the document context.\n\nSibling head components (``, ``) were not affected because they already routed slot text through the safe `textContent` path.\n\n### Affected versions\n\nAll currently supported versions of `nuxt` that ship the `` global component.\n\n### Patches\n\nFixed in `nuxt@4.4.7` (commit [`4b054e9d`]","public_affected_ranges":["< 3.21.7"]}],"null_published_at":"2026-11-08T19:53:44.065Z","source_updated_at":"2026-09-09T23:51:01.000Z","source_disclosed_at":"2026-06-16T23:38:47.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-11-01T22:54:12.705Z"},{"id":"NVI-00013800","kind":"vulnerability","title":"Cross-site scripting via  slot content in Nuxt's head components","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-m3q2-p4fw-w38m","CVE-2026-56317"],"plain_summary":"GitHub lists this reviewed advisory for nuxt, nuxt. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-0674c86e679bccd5982e359bd87baa3b"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-0674c86e679bccd5982e359bd87baa3b","url":"https://github.com/advisories/GHSA-m3q2-p4fw-w38m","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-m3q2-p4fw-w38m","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T22:54:12.705Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0674c86e679bccd5982e359bd87baa3b"],"technology":"nuxt","known_exclusions":[],"conditions_summary":"### Impact\n\nNuxt's globally registered `` component (from `@unhead/vue` head components, re-exported by Nuxt) wrote its default-slot content to the `innerHTML` of the `` head tag, bypassing the HTML escaping that `{{ }}` interpolation normally applies in Vue templates.\n\nApplications that placed untrusted, attacker-controllable data inside a `` slot, for example:\n\n```vue\n{{ route.query.banner }}\n```\n\nwould emit that value unescaped inside `` in the server-rendered HTML. With scripting enabled, the HTML parser treats `` content in `` under the \"in head noscript\" insertion mode: any tag other than `link`, `meta`, `noframes`, or `style` implicitly closes `` and is re-processed in the head. A payload such as `...` therefore escapes the element and executes in the document context.\n\nSibling head components (``, ``) were not affected because they already routed slot text through the safe `textContent` path.\n\n### Affected versions\n\nAll currently supported versions of `nuxt` that ship the `` global component.\n\n### Patches\n\nFixed in `nuxt@4.4.7` (commit [`4b054e9d`]","public_affected_ranges":[">= 4.0.0, < 4.4.7"]},{"certainty":"source_listed","source_ids":["sr-0674c86e679bccd5982e359bd87baa3b"],"technology":"nuxt","known_exclusions":[],"conditions_summary":"### Impact\n\nNuxt's globally registered `` component (from `@unhead/vue` head components, re-exported by Nuxt) wrote its default-slot content to the `innerHTML` of the `` head tag, bypassing the HTML escaping that `{{ }}` interpolation normally applies in Vue templates.\n\nApplications that placed untrusted, attacker-controllable data inside a `` slot, for example:\n\n```vue\n{{ route.query.banner }}\n```\n\nwould emit that value unescaped inside `` in the server-rendered HTML. With scripting enabled, the HTML parser treats `` content in `` under the \"in head noscript\" insertion mode: any tag other than `link`, `meta`, `noframes`, or `style` implicitly closes `` and is re-processed in the head. A payload such as `...` therefore escapes the element and executes in the document context.\n\nSibling head components (``, ``) were not affected because they already routed slot text through the safe `textContent` path.\n\n### Affected versions\n\nAll currently supported versions of `nuxt` that ship the `` global component.\n\n### Patches\n\nFixed in `nuxt@4.4.7` (commit [`4b054e9d`]","public_affected_ranges":["< 3.21.7"]}],"null_published_at":"2026-11-02T10:00:37.152Z","source_updated_at":"2026-09-09T23:51:01.000Z","source_disclosed_at":"2026-06-16T23:38:47.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-01T22:54:12.705Z"}],"next_cursor":null,"snapshot_revision":"42594"}