Quick answers
- Is CVE-2026-55886 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55886 being exploited in the wild.
- How severe is CVE-2026-55886?
- Medium severity, with a CVSS score of 4, published 1 July 2026.
- Which products and versions are affected?
- jodit (npm) < 4.12.26, SEMVER:introduced=0,fixed=4.12.26; Xdan Jodit Editor < 4.12.26.
- Is there a fix for CVE-2026-55886?
- Yes. jodit (npm): upgrade to 4.12.26 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-55886 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-55886?
- Check whether you run jodit (npm) or Xdan Jodit Editor at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- jodit (npm): upgrade to 4.12.26 or later
npm install jodit@4.12.26
Technical details
A prototype pollution vulnerability exists in Jodit Editor versions prior to 4.12.26. The root cause is located in the Jodit.modules.Helpers.set(chain, value, obj) function, which processes dot-separated strings to navigate object paths without filtering for sensitive keys such as __proto__, constructor, or prototype. If an application passes user-controlled input into this function, an attacker can reach and mutate the global Object.prototype. This can result in unexpected property injection, logic bypasses, or denial of service. The issue is resolved in version 4.12.26 by implementing a guard that rejects chains containing prototype-mutating segments.
Affected products
- xdan Jodit Editor < 4.12.26
Identifiers
- CVE-2026-55886
- GHSA-vpmm-x3fm-qr5c
Timeline
- 2026-06-16: advisory: GitHub advisory published by vendor
- 2026-07-01: disclosed: NVD publication date
- 2026-07-01: patched: Fix confirmed in version 4.12.26