Bug 2427941 (CVE-2026-22028) - CVE-2026-22028 preact: Preact: Arbitrary script execution via JSON serialization protection bypass
Summary: CVE-2026-22028 preact: Preact: Arbitrary script execution via JSON serializat...
Keywords:
Status: NEW
Alias: CVE-2026-22028
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2427983 2427984 2427985 2427991 2427992 2427993 2427994 2427995 2427996 2427997 2428003 2428004 2428005 2428007 2428008 2428010 2427975 2427976 2427977 2427978 2427979 2427980 2427981 2427982 2427986 2427987 2427988 2427989 2427990 2427998 2427999 2428000 2428001 2428002
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-01-08 15:02 UTC by OSIDB Bzimport
Modified: 2026-01-08 16:50 UTC (History)
49 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-01-08 15:02:13 UTC
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).


Note You need to log in before you can comment on or make changes to this bug.