dbcve.org
CWE-1321Weakness · CWE-1321

CVE-2026-55886

MEDIUM · 6.3 CVSS v4.0 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Jodit Editor is a WYSIWYG editor with written in pure TypeScript file and image editing capabilities. Versions prior to 4.12.26 are vulnerable to Prototype Pollution through Jodit.modules.Helpers.set(chain, value, obj), which walks the dot-separated chain, creating and following each path segment without filtering prototype-mutating keys. A chain that begins with (or contains) __proto__, constructor, or prototype lets the final assignment reach and mutate Object.prototype. Applications that pass a user-controlled or partially user-controlled key path into Jodit.modules.Helpers.set() could be vulnerable, causing unexpected property injection, logic bypass, denial of service, or secondary security issues. This issue has been fixed in version 4.12.26.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Jodit Editor versions before 4.12.26 contain a Prototype Pollution vulnerability in the Jodit.modules.Helpers.set() function. This function processes dot-separated key paths without filtering dangerous keys like __proto__, constructor, or prototype, allowing attackers to inject or modify Object.prototype properties when user-controlled input flows to this function.

MitigationUpdate Jodit Editor to version 4.12.26 or later. Additionally, audit code that passes user-supplied key paths to Jodit.modules.Helpers.set() to ensure input validation is applied before calling the function.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Jodit Editor version
    Locate the Jodit Editor package in your project (e.g., in package.json, node_modules/jodit/package.json, or the bundled JS file) and read the version number
    Affected if The version is lower than 4.12.26 (e.g., 4.12.25, 4.12.0, 4.x.x before 4.12.26)
  2. Find usage of Jodit.modules.Helpers.set()
    Search your codebase for calls to Jodit.modules.Helpers.set or Jodit.helpers.set (grep: 'Helpers.set' or '.set(' within Jodit-related files)
    Affected if This function is being called in your application code
  3. Inspect key path handling for dangerous properties
    Examine the code paths that pass keys to Helpers.set() - look for any key parameter that could contain dot notation like 'a.b' and trace whether it originates from user input (request parameters, form data, etc.)
    Affected if User-supplied input can reach Helpers.set() with unvalidated key paths containing strings like __proto__, constructor, or arbitrary property names

You are affected if your Jodit Editor version is below 4.12.26 AND your application passes unsanitized user input to the Jodit.modules.Helpers.set() function using dot-separated key paths.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Jodit Editor to version 4.12.26 or later. Additionally, audit code that passes user-supplied key paths to Jodit.modules.Helpers.set() to ensure input validation is applied before calling the function.

Recommended fix High confidence

4.12.26

  1. Identify the Jodit Editor version currently in use by checking package.json, lock files, or the Jodit version property
  2. Ensure the current version is below 4.12.26
  3. Update Jodit Editor to version 4.12.26 or later by running: npm install jodit@^4.12.26 or yarn add jodit@^4.12.26
  4. After upgrading, verify the application functions correctly and test that user input is not passed directly to Jodit.modules.Helpers.set() without validation
  5. Review code that uses Jodit.modules.Helpers.set() to ensure user-controlled keys are validated to reject __proto__, constructor, and prototype keys
Caveat Minor version upgrade typically low risk but review Jodit changelog for any behavioral changes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55886 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-55886 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data