A security flaw has been discovered in enquirer up to 2.4.1. Affected is the function Enquirer.set of the component Public Package API. The manipulation of the argument question.name results in improperly controlled modification of object prototype attributes. The attack can be launched remotely. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report.
CVE-2026-15187
Score 4.3 from GitHub Security Advisory (severity: LOW) published 2026-07-09. a secondary CVSS source baseline 4.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
- 4.3
- EG Score
- 4.3(high)
- EPSS
- 16.0%
- KEV
- Not listed
Published
July 9, 2026
Last Modified
July 9, 2026
Advisory Details (3)
Auto-updated Jul 9, 2026Prototype pollution through public `Enquirer` prompt flow when `question.name` contains `__proto__` · Issue #487 · enquirer/enquirer · GitHub
https://github.com/enquirer/enquirer/issues/487#issuecomment-4648521328Prototype pollution through public `Enquirer` prompt flow when `question.name` contains `__proto__` · Issue #487 · enquirer/enquirer · GitHub
https://github.com/enquirer/enquirer/issues/487GitHub - enquirer/enquirer: Stylish, intuitive and user-friendly prompts. Used by eslint, webpack, yarn, pm2, pnpm, RedwoodJS, FactorJS, salesforce, Cypress, Google Lighthouse, Generate, tencent cloudbase, lint-staged, gluegun, hygen, hardhat, AWS Amplify, GitHub Actions Toolkit, @airbnb/nimbus, and more! Please follow Enquirer's author: https://github.com/jonschlinkert · GitHub
https://github.com/enquirer/enquirer/Vendor Advisories for CVE-2026-15187(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 9× in last 7d / 9× 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-12 05:46 UTCEPSS rescore
- 2026-07-11 16:05 UTCEG score recompute
- 2026-07-11 16:05 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 15:51 UTCEG score recompute
- 2026-07-10 15:51 UTCGHSA enrichment
- 2026-07-09 17:00 UTCNVD updateCVSS v4 → 2.1
- 2026-07-09 15:37 UTCEG score recompute
- 2026-07-09 15:35 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-15187?
When was CVE-2026-15187 disclosed?
Is CVE-2026-15187 actively exploited?
What is the CVSS score of CVE-2026-15187?
How do I remediate CVE-2026-15187?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15187
Is Your Infrastructure Affected by CVE-2026-15187?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.