dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-15698

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 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
A vulnerability was determined in kofrasa mingo up to 7.2.1. This impacts the function update/updateOne/updateMany of the component Update API. Executing a manipulation of the argument Set can lead to improperly controlled modification of object prototype attributes. The attack may be launched remotely. Upgrading to version 7.2.2 will fix this issue. This patch is called fadc398251792c2ba441cbc539f359fc7943c0c2. It is recommended to upgrade the affected component.

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 · moderate confidence

Prototype pollution vulnerability in kofrasa mingo library versions up to 7.2.1. The Update API functions (update/updateOne/updateMany) fail to properly sanitize input, allowing attackers to manipulate object prototype attributes (__proto__, constructor) through the Set argument, potentially leading to code execution or data tampering.

MitigationUpgrade to version 7.2.2 which contains the fix (commit fadc398251792c2ba441cbc539f359fc7943c0c2). Until upgrade, validate and reject any user input containing __proto__, constructor, or other prototype-modifying properties in update operations.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 mingo library version
    Run 'npm list kofrasa/mingo' or inspect the package.json dependencies entry for the mingo package
    Affected if The installed version is 7.2.1 or earlier (any version up to and including 7.2.1)
  2. Locate Update API usage
    Search the codebase for calls to update(), updateOne(), or updateMany() methods provided by the mingo library
    Affected if These update functions are being called in the application code
  3. Trace user input to update operations
    Examine the data flow from HTTP request parameters, API payloads, or other user-controllable sources to the update/updateOne/updateMany function calls
    Affected if User-supplied data is passed directly as the Set argument to any of these update functions
  4. Inspect input sanitization for prototype properties
    Review the code handling update operations to determine whether it filters or rejects keys containing '__proto__', 'constructor', or other prototype-modifying property names before passing input to the update functions
    Affected if No validation exists to strip or reject prototype-modifying properties from the input before it reaches the update API

You are affected if the mingo library version is 7.2.1 or earlier AND user-controlled input flows into update/updateOne/updateMany without filtering out __proto__ or constructor properties.

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

Upgrade to version 7.2.2 which contains the fix (commit fadc398251792c2ba441cbc539f359fc7943c0c2). Until upgrade, validate and reject any user input containing __proto__, constructor, or other prototype-modifying properties in update operations.

Recommended fix High confidence

7.2.2

  1. Check the current version of mingo in your project by running 'npm list mingo' or reviewing package.json
  2. Update the mingo dependency in package.json to version 7.2.2 (e.g., "mingo": "^7.2.2" or "mingo": "7.2.2")
  3. Run 'npm install' or 'yarn install' to update the package
  4. Verify the installed version matches 7.2.2 using 'npm list mingo'
  5. Test your application's update/updateOne/updateMany functionality to ensure the fix works correctly

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15698 — 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-15698 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