Answer in brief
CVE-2026-88976 records a Medium severity (CVSS 6.1) vulnerability in @platejs/core HTML deserialization can trigger browser behavior during parsing. The current sources do not mark it as known exploited. The current feed maps udecode/plate (generic), @platejs/core (npm), @platejs/core (npm), @platejs/core (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps udecode/plate (generic), @platejs/core (npm), @platejs/core (npm), @platejs/core (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| udecode/plategeneric | < 53.3.11 || >= 54.0.0-beta.0, <= 54.0.0-beta.1 | Not reported |
| @platejs/corenpm | >=0 <53.3.11 | 53.3.11 |
| @platejs/corenpm | >=54.0.0-beta.0 | Not reported |
| @platejs/corenpm | <53.3.11 | 53.3.11 |
| @platejs/corenpm | >=54.0.0-beta.0,<=54.0.0-beta.1 | Not reported |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 16, 2026
Plate is a rich-text editor with AI and shadcn/ui. Prior to 53.3.11, and in the discontinued 54.0.0-beta.0 through 54.0.0-beta.1 builds, Plate core HTML deserialization APIs parse supplied HTML strings in the active document. When an application passes untrusted or cross-user HTML to these APIs, certain HTML attributes can trigger browser behavior before the HTML is converted into editor nodes. This can allow attacker-controlled script to execute in the consuming application's origin when another user loads the deserialized content. This issue is fixed in version 53.3.11.
Quoted source text, attributed separately from HOL analysis.