# CVE-2026-15187: enquirer Public Package API Enquirer.set prototype pollution

> Remote attackers can exploit prototype pollution in Enquirer.set to execute arbitrary code or escalate privileges within applications using this library.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jul 2026
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-5727-r6pv-59f5

## What is CVE-2026-15187?

CVE-2026-15187 is a medium-severity code injection vulnerability in enquirer, published on 9 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2026-15187?


## How do I fix CVE-2026-15187?

Upgrade to a fixed version.

## Is CVE-2026-15187 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15187 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15187 and fix it if it is affected.

What it is: CVE-2026-15187 is a medium-severity code injection vulnerability in enquirer, published on 9 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15187 exists.

Affected product: enquirer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-15187/ (Markdown: https://insights.sbomify.com/CVE-2026-15187/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-15187
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-15187
- OSV: https://osv.dev/vulnerability/CVE-2026-15187

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-15187/
Summaries are generated and may contain mistakes; the official description above is the record.