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.
CVE-2026-15699
Score 6.3 from GitHub Security Advisory (severity: LOW) published 2026-07-14. a secondary CVSS source baseline 6.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(high)
- EPSS
- 17.0%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 14, 2026
Advisory Details (3)
Auto-updated Jul 15, 2026Prototype Pollution via `nlp.extend()` Plugin Model Merge · Issue #1208 · spencermountain/compromise · GitHub
https://github.com/spencermountain/compromise/issues/1208commit b4644ab71797 (spencermountain/compromise)
Patch available: spencermountain/compromise 14.16.0 (contains commit b4644ab71797)
https://github.com/spencermountain/compromise/commit/b4644ab7179700df0607521f61c1ee9b5f78d89dGitHub - spencermountain/compromise: modest natural-language processing · GitHub
https://github.com/spencermountain/compromise/Vendor Advisories for CVE-2026-15699(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 15:34 UTCEG score recompute
- 2026-07-15 15:34 UTCGHSA enrichment
- 2026-07-14 19:21 UTCNVD updateCVSS v4 → 2.1
- 2026-07-14 18:10 UTCMITRE cvelistV5CVSS v4 → 5.3
- 2026-07-14 17:20 UTCNVD updateCVSS v4 → 2.1
- 2026-07-14 16:10 UTCEG score recompute
- 2026-07-14 16:10 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-94
- CVE-2006-1359NVD 0.0EG 9.0EPSS 99%NONE
- CVE-2005-1921NVD 0.0EG 9.0EPSS 100%NONE
- CVE-2005-3302EG 7.3HIGH
- CVE-2005-1876EG 4.5MEDIUM
- CVE-2003-1599EG 0.0NONE
- CVE-2006-1318EG 0.0EPSS 96%NONE
- CVE-2006-1301EG 0.0EPSS 95%NONE
- CVE-2006-1308EG 0.0EPSS 95%NONE
- CVE-2006-1309EG 0.0EPSS 95%NONE
- CVE-2006-1304EG 0.0EPSS 95%NONE
Frequently asked(5)
What is CVE-2026-15699?
When was CVE-2026-15699 disclosed?
Is CVE-2026-15699 actively exploited?
What is the CVSS score of CVE-2026-15699?
How do I remediate CVE-2026-15699?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15699
Is Your Infrastructure Affected by CVE-2026-15699?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.