VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

ckeditor5: vulnerability history, versions and safety

ckeditor5 is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 92 releases, from Feb 2023 to Sep 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded M2 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ckeditor5 vulnerabilities

Vulert verdict on ckeditor5 49.0.0 i

Updated on 23 Oct 2026

Good news: 49.0.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 80/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

What to do: Stay on 49.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 49.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 49.0.0 — unaffected i
  • Vulnerabilities on record 3 over 2 years · 0 in the last year i
  • Latest disclosure 03 Sep 2025 i
  • Highest CVSS 7.2 i
  • With no published fix 0 i
  • Depended on by 49 packages i
  • Stars 10,516 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence non-standard i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for ckeditor5, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.0.0-nightly-20261023.0 23 Oct 2026 M1 non-standard Yes Details →
0.0.0-nightly-20261022.0 22 Oct 2026 M1 non-standard Yes Details →
0.0.0-nightly-20261021.0 21 Oct 2026 M1 non-standard Yes Details →
0.0.0-nightly-20261020.0 20 Oct 2026 M1 non-standard Yes Details →
0.0.0-nightly-20261019.0 19 Oct 2026 M1 non-standard Yes Details →
0.0.0-nightly-20261018.0 18 Oct 2026 M1 non-standard Yes Details →
0.0.0-nightly-20261017.0 17 Oct 2026 M1 non-standard Yes Details →
0.0.0-nightly-20261016.0 16 Oct 2026 M1 non-standard Yes Details →
0.0.0-nightly-20261015.0 15 Oct 2026 M1 non-standard Yes Details →
0.0.0-nightly-20261014.0 14 Oct 2026 M1 non-standard Yes Details →
0.0.0-nightly-20261013.0 13 Oct 2026 M1 non-standard Yes Details →
0.0.0-nightly-20261012.0 12 Oct 2026 M1 non-standard Yes Details →
0.0.0-nightly-20261011.0 11 Oct 2026 M1 non-standard Yes Details →
0.0.0-nightly-20261010.0 10 Oct 2026 M1 non-standard Yes Details →
0.0.0-nightly-20261009.0 09 Oct 2026 M1 non-standard Yes Details →
49.0.0 08 Oct 2026 none non-standard — Details →
0.0.0-nightly-20261008.0 08 Oct 2026 M1 non-standard Yes Details →
49.0.0-alpha.11 08 Oct 2026 none non-standard — Details →
49.0.0-alpha.10 07 Oct 2026 none non-standard — Details →
49.0.0-alpha.9 07 Oct 2026 none non-standard — Details →
0.0.0-nightly-20261007.0 07 Oct 2026 M1 non-standard Yes Details →
49.0.0-alpha.8 07 Oct 2026 none non-standard — Details →
49.0.0-alpha.7 06 Oct 2026 none non-standard — Details →
0.0.0-nightly-20261006.0 06 Oct 2026 M1 non-standard Yes Details →
49.0.0-alpha.6 06 Oct 2026 none non-standard — Details →
0.0.0-nightly-20261005.0 05 Oct 2026 M1 non-standard Yes Details →
49.0.0-alpha.5 05 Oct 2026 none non-standard — Details →
0.0.0-nightly-20261004.0 04 Oct 2026 M1 non-standard Yes Details →
49.0.0-alpha.4 04 Oct 2026 none non-standard — Details →
0.0.0-nightly-20261003.0 03 Oct 2026 M1 non-standard Yes Details →
49.0.0-alpha.3 03 Oct 2026 none non-standard — Details →
0.0.0-nightly-20261002.0 02 Oct 2026 M1 non-standard Yes Details →
49.0.0-alpha.2 02 Oct 2026 none non-standard — Details →
0.0.0-nightly-20261001.2 01 Oct 2026 M1 non-standard Yes Details →
0.0.0-nightly-20261001.1 01 Oct 2026 M1 non-standard Yes Details →
0.0.0-nightly-20261001.0 01 Oct 2026 M1 non-standard Yes Details →
49.0.0-alpha.1 01 Oct 2026 none non-standard — Details →
49.0.0-alpha.0 30 Sep 2026 none non-standard — Details →
0.0.0-nightly-20260930.0 30 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260929.0 29 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260928.0 28 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260927.0 27 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260926.0 26 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260925.0 25 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260924.0 24 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260923.1 23 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260923.0 23 Sep 2026 M1 non-standard Yes Details →
47.7.5 22 Sep 2026 none non-standard — Details →
48.5.2 22 Sep 2026 none non-standard — Details →
0.0.0-nightly-20260922.0 22 Sep 2026 M1 non-standard Yes Details →
48.5.2-alpha.0 22 Sep 2026 none non-standard — Details →
0.0.0-nightly-20260921.0 21 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260920.0 20 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260919.0 19 Sep 2026 M1 non-standard Yes Details →
47.7.5-alpha.0 18 Sep 2026 none non-standard — Details →
0.0.0-nightly-20260918.0 18 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260917.0 17 Sep 2026 M1 non-standard Yes Details →
47.7.4 16 Sep 2026 none non-standard — Details →
48.5.1 16 Sep 2026 none non-standard — Details →
0.0.0-nightly-20260916.0 16 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260915.0 15 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260914.0 14 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260913.0 13 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260912.0 12 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260911.0 11 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260910.0 10 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260909.0 09 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260908.0 08 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-next-20260907.0 07 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260907.0 07 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-next-20260906.0 06 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260906.0 06 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-next-20260905.0 05 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260905.0 05 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-next-20260904.0 04 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260904.0 04 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-next-20260903.0 03 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260903.0 03 Sep 2026 M1 non-standard Yes Details →
48.5.0 02 Sep 2026 none non-standard — Details →
0.0.0-nightly-next-20260902.0 02 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260902.0 02 Sep 2026 M1 non-standard Yes Details →
48.5.0-alpha.7 02 Sep 2026 none non-standard — Details →
0.0.0-nightly-next-20260901.0 01 Sep 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260901.0 01 Sep 2026 M1 non-standard Yes Details →
48.5.0-alpha.6 01 Sep 2026 none non-standard — Details →
0.0.0-nightly-next-20260831.0 31 Aug 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260831.0 31 Aug 2026 M1 non-standard Yes Details →
48.5.0-alpha.5 31 Aug 2026 none non-standard — Details →
0.0.0-nightly-next-20260830.0 30 Aug 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260830.0 30 Aug 2026 M1 non-standard Yes Details →
48.5.0-alpha.4 30 Aug 2026 none non-standard — Details →
0.0.0-nightly-next-20260829.0 29 Aug 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260829.0 29 Aug 2026 M1 non-standard Yes Details →
48.5.0-alpha.3 29 Aug 2026 none non-standard — Details →
0.0.0-nightly-next-20260828.0 28 Aug 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260828.0 28 Aug 2026 M1 non-standard Yes Details →
48.5.0-alpha.2 28 Aug 2026 none non-standard — Details →
0.0.0-nightly-next-20260827.0 27 Aug 2026 M1 non-standard Yes Details →
0.0.0-nightly-20260827.0 27 Aug 2026 M1 non-standard Yes Details →
48.5.0-alpha.1 27 Aug 2026 none non-standard — Details →
48.5.0-alpha.0 26 Aug 2026 none — — Details →
0.0.0-nightly-next-20260826.0 26 Aug 2026 M1 — Yes Details →
0.0.0-nightly-20260826.0 26 Aug 2026 M1 — Yes Details →
0.0.0-nightly-next-20260825.0 25 Aug 2026 M1 — Yes Details →
0.0.0-nightly-20260825.0 25 Aug 2026 M1 — Yes Details →
0.0.0-nightly-next-20260824.0 24 Aug 2026 M1 — Yes Details →
0.0.0-nightly-20260824.0 24 Aug 2026 M1 — Yes Details →
0.0.0-nightly-20260823.0 23 Aug 2026 M1 — Yes Details →
0.0.0-nightly-next-20260823.0 23 Aug 2026 M1 — Yes Details →
0.0.0-nightly-next-20260822.0 22 Aug 2026 M1 — Yes Details →
0.0.0-nightly-20260822.0 22 Aug 2026 M1 — Yes Details →
0.0.0-nightly-next-20260821.0 21 Aug 2026 M1 — Yes Details →
0.0.0-nightly-20260821.0 21 Aug 2026 M1 — Yes Details →
0.0.0-nightly-next-20260820.0 20 Aug 2026 M1 — Yes Details →
0.0.0-nightly-20260820.0 20 Aug 2026 M1 — Yes Details →
0.0.0-nightly-next-20260819.0 19 Aug 2026 M1 — Yes Details →
0.0.0-nightly-20260819.0 19 Aug 2026 M1 — Yes Details →
0.0.0-nightly-next-20260818.0 18 Aug 2026 M1 — Yes Details →
0.0.0-nightly-20260818.0 18 Aug 2026 M1 — Yes Details →
0.0.0-nightly-next-20260817.0 17 Aug 2026 M1 — Yes Details →

The newest 120 of 1,891 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2024 1
  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for ckeditor5

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-45613: CKEditor 5 Clipboard Package Cross-Site Scripting Vulnerability 7.2 medium 43.1.1 25 Sep 2024
CVE-2022-48110: Cross-site scripting in CKEditor5 6.1 medium 36.0.0 13 Feb 2023
CVE-2025-58064: CKEditor 5 Clipboard Package XSS Vulnerability 2.3 low 46.0.3 03 Sep 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About ckeditor5

Is ckeditor5 safe to use?

Vulert records 3 vulnerabilities for ckeditor5 in npm: 0 critical, 0 high, 2 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is ckeditor5's Vulert package health score?

Vulert scores ckeditor5 80/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of ckeditor5 affected?

No. 49.0.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of ckeditor5 should I use?

49.0.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does ckeditor5 have?

3 vulnerabilities are recorded for ckeditor5 in the npm ecosystem: 0 critical, 0 high, 2 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new ckeditor5 vulnerabilities disclosed?

0 vulnerabilities were recorded for ckeditor5 in the last 12 months, and the oldest entry in this database dates to 13 Feb 2023. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of ckeditor5 are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor ckeditor5 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the ckeditor5 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.