Prototype pollution via unsafe question.name path traversal
Published Jul 9, 2026 · Updated Jul 9, 2026
Prototype pollution in Enquirer 2.4.0 and 2.4.1 allows remote authenticated users to modify Object.prototype via question.name. Enquirer.set passes question.name to an internal nested-path setter that traverses proto without rejecting dangerous segments, writing to Object.prototype. Reachability requires a consuming application to accept attacker-controlled prompt definitions; resulting effects are bounded by that application's use of inherited properties.
Summary
What happened
Prototype pollution in Enquirer 2.4.0 and 2.4.1 allows remote authenticated users to modify Object.prototype via question.name. Enquirer.set passes question.name to an internal nested-path setter that traverses proto without rejecting dangerous segments, writing to Object.prototype. Reachability requires a consuming application to accept attacker-controlled prompt definitions; resulting effects are bounded by that application's use of inherited properties.
The record
- CVE
- CVE-2026-15187
- Published
- Jul 9, 2026
- Updated
- Jul 9, 2026
- Vendor
- Enquirer
- Product
- Enquirer
- Classifications
- CWE-94, CWE-1321
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 9, 2026CVE publishedPublication date reported by the CVE source.
- Jul 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.4.0
- Affected versionversion=2.4.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Enquirer question.name prototype-pollution demonstrationproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo