Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA GitHub_M

CVE-2026-116687: CKEditor: Cross-site scripting (XSS) in the engine package

LowCVSS 3.1 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 12/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: @ckeditor/ckeditor5-engine (npm) 47.7.4, 48.5.1; ckeditor5 (npm) 47.7.4, 48.5.1.

Low priority for now. Upgrade to @ckeditor/ckeditor5-engine (npm) 47.7.4, 48.5.1; ckeditor5 (npm) 47.7.4, 48.5.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

CKEditor 5 is a modern JavaScript rich-text editor with an MVC architecture. From 29.0.0 until 47.7.4 and 48.5.1, specially crafted markup can trigger cross-site scripting when General HTML Support is enabled and specifically configured to allow object content. Processing that content can execute attacker-controlled JavaScript in a browser context isolated from the origin of the application embedding the editor. This issue is fixed in versions 47.7.4 and 48.5.1.

Published
Oct 27, 2026
Updated
Nov 3, 2026
EPSS
0.2% · 16th percentile

Report tools

JSON

Action score

12

Monitor

Low priority for now.

CVSS
12 / 40 · 3.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
3.1
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-116687

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Is the CKEditor 5 on your site affected?Scan JavaScript libraries

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is the CKEditor 5 on your site affected?Scan JavaScript libraries

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Is the CKEditor 5 on your site affected?

The free JavaScript library scanner reads the CKEditor 5 version from the files your site loads, matches this record and other known vulnerabilities, and gives the safe version on the same branch. If the version can't be read, it says so. No account needed.

Scan JavaScript libraries

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • ckeditor ckeditor5

    • >= 29.0.0, < 47.7.4, >= 48.0.0, < 48.5.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
npm@ckeditor/ckeditor5-enginefrom 29.0.0 · before 47.7.447.7.4
npm@ckeditor/ckeditor5-enginefrom 48.0.0 · before 48.5.148.5.1
npmckeditor5from 29.0.0 · before 47.7.447.7.4
npmckeditor5from 48.0.0 · before 48.5.148.5.1

Other highest-scoring records for the same primary product.

  • CVE-2026-116688CKEditor: Cross-site scripting (XSS) in the engine package
    32Monitor
  • CVE-2021-21254Regular expression Denial of Service in Markdown plugin
    27Monitor
  • CVE-2026-28343CKEditor: Cross-site scripting (XSS) in the HTML Support package
    24Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2024-45613Sep 25, 2024 · CKEditor 5 has Cross-site Scripting vulnerability in the clipboard package
    20Monitor
  • ← EarlierCVE-2025-25299Feb 20, 2025 · Cross-site scripting (XSS) in the real-time collaboration package
    9Monitor
  • ← EarlierCVE-2025-58064Sep 4, 2025 · CKEditor is susceptible to Cross-Site Scripting (XSS) through its clipboard package
    9Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
npm:@ckeditor/ckeditor5-engine47.7.4Package registry (OSV)
npm:@ckeditor/ckeditor5-engine48.5.1Package registry (OSV)
npm:ckeditor547.7.4Package registry (OSV)
npm:ckeditor548.5.1Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 13, 2026+17 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-1166880 days apartCKEditor: Cross-site scripting (XSS) in the engine package
    32Monitor
  • CVE-2026-28343236 days apartCKEditor: Cross-site scripting (XSS) in the HTML Support package
    24Monitor
  • CVE-2025-58064418 days apartCKEditor is susceptible to Cross-Site Scripting (XSS) through its clipboard package
    9Monitor

Not on record for this CVE: researcher credit · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
Low
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N

nvd-secondary

Root cause

User content is inserted into the page as HTML. The browser interprets the content as code rather than data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
commentEl.innerHTML = comment.body;

Fixed

ts
commentEl.textContent = comment.body;

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓
  3. Exploit maturity— → none

For records you follow, these changes also arrive as notifications. →

References

All records