dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-15699

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 identified in spencermountain compromise up to 14.15.1. Affected is the function nlp.extend of the file src/API/extend.js of the component Public Root API. The manipulation of the argument plugin leads to improperly controlled modification of object prototype attributes. Remote exploitation of the attack is possible. The exploit is publicly available and might be used. The identifier of the patch is b4644ab7179700df0607521f61c1ee9b5f78d89d. Applying a patch is the recommended action to fix this issue. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.

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

This is a Prototype Pollution vulnerability in the spencermountain/compromise NLP library. The nlp.extend function in src/API/extend.js does not properly validate the plugin argument, allowing attackers to inject properties into the Object prototype through improperly controlled modification. This can cause denial of service or enable further attacks depending on library usage.

MitigationUpgrade to the patched version of compromise (version 14.15.2 or later) which addresses the improper input validation in the nlp.extend function. If immediate upgrade is not possible, implement input sanitization on the plugin argument to reject prototype-modifying properties.

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 compromise library installation
    Check your project's node_modules/spencermountain-compromise/package.json or run 'npm list compromise' to see if the library is installed
    Affected if The library is not present in the project dependencies
  2. Check installed compromise version
    Run 'npm list compromise' or inspect node_modules/spencermountain-compromise/package.json to find the installed version number
    Affected if The installed version is lower than 14.15.2 (vulnerable versions are below 14.15.2)
  3. Verify nlp.extend is being used
    Search your codebase for calls to nlp.extend, nlp.plugin, or similar extension methods from the compromise library
    Affected if The codebase contains calls to nlp.extend or nlp.plugin that accept external/plugin input
  4. Inspect plugin input handling
    Review the code handling plugin arguments passed to nlp.extend to see if input is validated before being passed
    Affected if Plugin arguments are passed directly to nlp.extend without sanitization or validation checks for prototype-modifying properties
  5. Check for prototype pollution in runtime
    Run a JavaScript probe: after importing nlp, test whether Object.prototype can be modified via nlp.extend({__proto__: {test: true}})
    Affected if The test reveals that Object.prototype.test becomes truthy after the call, confirming prototype pollution is possible

You are affected if the compromise library version is below 14.15.2 AND your code uses nlp.extend with unvalidated external input that could contain prototype-modifying 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 the patched version of compromise (version 14.15.2 or later) which addresses the improper input validation in the nlp.extend function. If immediate upgrade is not possible, implement input sanitization on the plugin argument to reject prototype-modifying properties.

Recommended fix Moderate confidence

compromise version > 14.15.1 (latest stable release)

  1. 1. Identify the installed version of the spencermountain/compromise package in your project (check package.json or run npm list compromise)
  2. 2. If the version is 14.15.1 or lower, update to the latest version using: npm install compromise@latest
  3. 3. Alternatively, update to a specific version higher than 14.15.1 using: npm install compromise@>14.15.1
  4. 4. After updating, run your test suite to verify the fix doesn't break existing functionality
  5. 5. Rebuild and redeploy your application
Caveat Review changelog for potential breaking changes between 14.15.1 and the target version, particularly around plugin loading behavior in nlp.extend

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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