VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

cyberchef: vulnerability history, versions and safety

cyberchef is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 116 releases, from Aug 2019 to Sep 2026. 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 H1 M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 24 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all cyberchef vulnerabilities

Vulert verdict on cyberchef 11.5.0 i

Updated on 22 Oct 2026

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

Package health score 79/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Active

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

  • Current release 11.5.0 — unaffected i
  • Vulnerabilities on record 3 over 7 years · 2 in the last year i
  • Latest disclosure 24 Sep 2026 i
  • Highest CVSS 7.2 i
  • With no published fix 0 i
  • Stars 36,174 i
  • OpenSSF scorecard 7/10 i
  • Last release 1 month ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 cyberchef, 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
11.5.0 18 Sep 2026 none Apache-2.0 — Details →
11.4.0 18 Aug 2026 none Apache-2.0 — Details →
11.3.0 24 Jul 2026 none Apache-2.0 — Details →
11.2.0 17 Jun 2026 none Apache-2.0 — Details →
11.1.0 13 Jun 2026 M1 Apache-2.0 Yes Details →
11.0.0 28 Apr 2026 M1 Apache-2.0 Yes Details →
10.24.0 27 Apr 2026 H1 M1 Apache-2.0 Yes Details →
10.23.0 07 Apr 2026 H1 M1 Apache-2.0 Yes Details →
10.22.1 12 Feb 2026 H1 M1 Apache-2.0 Yes Details →
10.22.0 11 Feb 2026 H1 M1 Apache-2.0 Yes Details →
10.19.4 23 Oct 2024 H1 M1 Apache-2.0 Yes Details →
10.19.2 14 Aug 2024 H1 M1 Apache-2.0 Yes Details →
10.18.9 21 Jun 2024 H1 M1 Apache-2.0 Yes Details →
10.19.0 21 Jun 2024 H1 M1 Apache-2.0 Yes Details →
10.18.8 11 Jun 2024 H1 M1 Apache-2.0 Yes Details →
10.18.6 16 May 2024 H1 M1 Apache-2.0 Yes Details →
10.18.5 16 May 2024 H1 M1 Apache-2.0 Yes Details →
10.18.3 24 Apr 2024 H1 M1 Apache-2.0 Yes Details →
10.17.0 13 Apr 2024 H1 M1 Apache-2.0 Yes Details →
10.16.0 12 Apr 2024 H1 M1 Apache-2.0 Yes Details →
10.15.1 05 Apr 2024 H1 M1 Apache-2.0 Yes Details →
10.15.0 02 Apr 2024 H1 M1 Apache-2.0 Yes Details →
10.14.0 31 Mar 2024 H1 M1 Apache-2.0 Yes Details →
10.13.0 30 Mar 2024 H1 M1 Apache-2.0 Yes Details →
10.10.0 27 Mar 2024 H1 M1 Apache-2.0 Yes Details →
10.9.0 26 Mar 2024 H1 M1 Apache-2.0 Yes Details →
10.8.2 21 Feb 2024 H1 M1 Apache-2.0 Yes Details →
10.8.0 13 Feb 2024 H1 M1 Apache-2.0 Yes Details →
10.7.0 09 Feb 2024 H1 M1 Apache-2.0 Yes Details →
10.6.0 03 Feb 2024 H1 M1 Apache-2.0 Yes Details →
10.5.2 14 Jul 2023 H1 M1 Apache-2.0 Yes Details →
10.4.0 24 Mar 2023 H1 M1 Apache-2.0 Yes Details →
10.3.0 24 Mar 2023 H1 M1 Apache-2.0 Yes Details →
10.2.0 23 Mar 2023 H1 M1 Apache-2.0 Yes Details →
10.1.0 23 Mar 2023 H1 M1 Apache-2.0 Yes Details →
10.0.1 23 Mar 2023 H1 M1 Apache-2.0 Yes Details →
10.0.0 22 Mar 2023 H1 M1 Apache-2.0 Yes Details →
9.55.0 09 Dec 2022 H1 M1 Apache-2.0 Yes Details →
9.54.0 25 Nov 2022 H1 M1 Apache-2.0 Yes Details →
9.53.0 25 Nov 2022 H1 M1 Apache-2.0 Yes Details →
9.52.1 25 Nov 2022 H1 M1 Apache-2.0 Yes Details →
9.52.0 25 Nov 2022 H1 M1 Apache-2.0 Yes Details →
9.50.12 25 Nov 2022 H1 M1 Apache-2.0 Yes Details →
9.50.11 25 Nov 2022 H1 M1 Apache-2.0 Yes Details →
9.50.10 25 Nov 2022 H1 M1 Apache-2.0 Yes Details →
9.50.9 25 Nov 2022 H1 M1 Apache-2.0 Yes Details →
9.50.7 25 Nov 2022 H1 M1 Apache-2.0 Yes Details →
9.50.8 25 Nov 2022 H1 M1 Apache-2.0 Yes Details →
9.50.6 25 Nov 2022 H1 M1 Apache-2.0 Yes Details →
9.50.5 25 Nov 2022 H1 M1 Apache-2.0 Yes Details →
9.50.4 25 Nov 2022 H1 M1 Apache-2.0 Yes Details →
9.50.3 25 Nov 2022 H1 M1 Apache-2.0 Yes Details →
9.50.2 25 Nov 2022 H1 M1 Apache-2.0 Yes Details →
9.50.1 25 Nov 2022 H1 M1 Apache-2.0 Yes Details →
9.50.0 25 Nov 2022 H1 M1 Apache-2.0 Yes Details →
9.49.2 25 Nov 2022 H1 M1 Apache-2.0 Yes Details →
9.49.1 25 Nov 2022 H1 M1 Apache-2.0 Yes Details →
9.49.0 11 Nov 2022 H1 M1 Apache-2.0 Yes Details →
9.48.0 14 Oct 2022 H1 M1 Apache-2.0 Yes Details →
9.47.5 14 Oct 2022 H1 M1 Apache-2.0 Yes Details →
9.47.4 14 Oct 2022 H1 M1 Apache-2.0 Yes Details →
9.47.3 14 Oct 2022 H1 M1 Apache-2.0 Yes Details →
9.47.2 14 Oct 2022 H1 M1 Apache-2.0 Yes Details →
9.47.1 14 Oct 2022 H1 M1 Apache-2.0 Yes Details →
9.47.0 14 Oct 2022 H1 M1 Apache-2.0 Yes Details →
9.46.7 14 Oct 2022 H1 M1 Apache-2.0 Yes Details →
9.46.6 14 Oct 2022 H1 M1 Apache-2.0 Yes Details →
9.46.5 16 Sep 2022 H1 M1 Apache-2.0 Yes Details →
9.46.4 09 Sep 2022 H1 M1 Apache-2.0 Yes Details →
9.46.3 09 Sep 2022 H1 M1 Apache-2.0 Yes Details →
9.46.2 09 Sep 2022 H1 M1 Apache-2.0 Yes Details →
9.46.1 09 Sep 2022 H1 M1 Apache-2.0 Yes Details →
9.46.0 08 Jul 2022 H1 M1 Apache-2.0 Yes Details →
9.45.0 08 Jul 2022 H1 M1 Apache-2.0 Yes Details →
9.44.0 08 Jul 2022 H1 M1 Apache-2.0 Yes Details →
9.43.0 08 Jul 2022 H1 M1 Apache-2.0 Yes Details →
9.42.0 08 Jul 2022 H1 M1 Apache-2.0 Yes Details →
9.41.0 08 Jul 2022 H1 M1 Apache-2.0 Yes Details →
9.40.0 08 Jul 2022 H1 M1 Apache-2.0 Yes Details →
9.39.6 08 Jul 2022 H1 M1 Apache-2.0 Yes Details →
9.39.5 08 Jul 2022 H1 M1 Apache-2.0 Yes Details →
9.39.4 08 Jul 2022 H1 M1 Apache-2.0 Yes Details →
9.39.3 08 Jul 2022 H1 M1 Apache-2.0 Yes Details →
9.39.2 08 Jul 2022 H1 M1 Apache-2.0 Yes Details →
9.39.1 09 Jun 2022 H1 M1 Apache-2.0 Yes Details →
9.39.0 09 Jun 2022 H1 M1 Apache-2.0 Yes Details →
9.38.9 08 Jun 2022 H1 M1 Apache-2.0 Yes Details →
9.38.8 08 Jun 2022 H1 M1 Apache-2.0 Yes Details →
9.38.7 06 Jun 2022 H1 M1 Apache-2.0 Yes Details →
9.38.6 03 Jun 2022 H1 M1 Apache-2.0 Yes Details →
9.38.5 03 Jun 2022 H1 M1 Apache-2.0 Yes Details →
9.38.4 03 Jun 2022 H1 M1 Apache-2.0 Yes Details →
9.38.2 03 Jun 2022 H1 M1 Apache-2.0 Yes Details →
9.38.1 03 Jun 2022 H1 M1 Apache-2.0 Yes Details →
9.38.0 30 May 2022 H1 M1 Apache-2.0 Yes Details →
9.37.3 14 Apr 2022 H1 M1 Apache-2.0 Yes Details →
9.37.2 14 Apr 2022 H1 M1 Apache-2.0 Yes Details →
9.37.1 14 Apr 2022 H1 M1 Apache-2.0 Yes Details →
9.37.0 29 Mar 2022 H1 M1 Apache-2.0 Yes Details →
9.36.1 29 Mar 2022 H1 M1 Apache-2.0 Yes Details →
9.36.0 29 Mar 2022 H1 M1 — Yes Details →
9.35.0 28 Mar 2022 H1 M1 — Yes Details →
9.34.2 28 Mar 2022 H1 M1 — Yes Details →
9.34.1 28 Mar 2022 H1 M1 — Yes Details →
9.34.0 28 Mar 2022 H1 M1 — Yes Details →
9.33.1 28 Mar 2022 H1 M1 — Yes Details →
9.33.0 28 Mar 2022 H1 M1 — Yes Details →
9.32.3 03 Sep 2021 H1 M1 — Yes Details →
9.32.2 26 Aug 2021 H1 M1 — Yes Details →
9.32.1 19 Aug 2021 H1 M1 — Yes Details →
9.32.0 18 Aug 2021 H1 M1 — Yes Details →
9.30.0 10 Aug 2021 H1 M1 — Yes Details →
9.28.0 26 Mar 2021 H1 M1 — Yes Details →
9.27.6 23 Feb 2021 H1 M1 — Yes Details →
9.27.5 22 Feb 2021 H1 M1 — Yes Details →
9.27.4 22 Feb 2021 H1 M1 — Yes Details →
9.27.2 16 Feb 2021 H1 M1 — Yes Details →
9.27.1 12 Feb 2021 H1 M1 — Yes Details →
9.27.0 12 Feb 2021 H1 M1 — Yes Details →
9.26.3 12 Feb 2021 H1 M1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for cyberchef

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-42615: CyberChef Cross-site Scripting Vulnerability 7.2 high 11.0.0 29 Apr 2026
CVE-2019-15532: Cross-Site Scripting in cyberchef 6.1 medium 8.31.3 27 Aug 2019
CVE-2026-57439: CyberChef Prototype Pollution in Series Chart Operation 5.0 medium 11.2.0 24 Sep 2026

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 cyberchef

Is cyberchef safe to use?

Vulert records 3 vulnerabilities for cyberchef in npm: 0 critical, 1 high, 2 medium and 0 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 cyberchef's Vulert package health score?

Vulert scores cyberchef 79/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 cyberchef affected?

No. 11.5.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 cyberchef should I use?

11.5.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 cyberchef have?

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

How often are new cyberchef vulnerabilities disclosed?

2 vulnerabilities were recorded for cyberchef in the last 12 months, and the oldest entry in this database dates to 27 Aug 2019. 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 cyberchef 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 cyberchef for upcoming vulnerabilities?

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