enquirer up to 2.4.1 Public Package API Enquirer.set question.name prototype pollution
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 2.10+ |
Summary
A vulnerability identified as critical has been detected in enquirer up to 2.4.1. Affected by this vulnerability is the function Enquirer.set of the component Public Package API. This manipulation of the argument question.name causes prototype pollution.
This vulnerability appears as CVE-2026-15187. The attack may be initiated remotely. In addition, an exploit is available.
The project was informed of the problem early through an issue report.
Details
A vulnerability has been found in enquirer up to 2.4.1 and classified as problematic. Affected by this vulnerability is the function Enquirer.set of the component Public Package API. The manipulation of the argument question.name with an unknown input leads to a prototype pollution vulnerability. The CWE definition for the vulnerability is CWE-1321. The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype. As an impact it is known to affect integrity.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-15187. The exploitation appears to be easy. The attack can be launched remotely. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1059 for this issue.
It is possible to download the exploit at github.com. It is declared as proof-of-concept. The project was informed of the problem early through an issue report.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 3.9
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Prototype pollutionCWE: CWE-1321 / CWE-94 / CWE-74
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
07/09/2026 Advisory disclosed07/09/2026 VulDB entry created
07/09/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 487
Status: Not defined
CVE: CVE-2026-15187 (🔒)
GCVE (CVE): GCVE-0-2026-15187
GCVE (VulDB): GCVE-100-377113
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 07/09/2026 07:19Changes: 07/09/2026 07:19 (25), 07/09/2026 07:20 (32)
Complete: 🔍
Submitter: Dremig
Cache ID: 216::103
Submit
Accepted
- Submit #851357: Node.js enquirer 2.4.1 Prototype Pollution (by Dremig)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.