Prototype pollution via unfiltered mailbox field merges
Published May 4, 2026 · Updated May 4, 2026
Prototype pollution in EvoMap Evolver before 1.69.3 allows local users to alter JavaScript object behavior through mailbox data. The mailbox store's _applyUpdate() and _updateRecord() methods pass fields from messages.jsonl to Object.assign() without rejecting proto, constructor, or prototype keys. Exploitation requires write access to the mailbox persistence file and can corrupt application logic, expose limited data, or interrupt the process.
Summary
What happened
Prototype pollution in EvoMap Evolver before 1.69.3 allows local users to alter JavaScript object behavior through mailbox data. The mailbox store's _applyUpdate() and _updateRecord() methods pass fields from messages.jsonl to Object.assign() without rejecting proto, constructor, or prototype keys. Exploitation requires write access to the mailbox persistence file and can corrupt application logic, expose limited data, or interrupt the process.
The record
- CVE
- CVE-2026-42077
- Published
- May 4, 2026
- Updated
- May 4, 2026
- Vendor
- EvoMap
- Product
- Evolver
- Classifications
- CWE-1321, T1565.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 4, 2026CVE publishedPublication date reported by the CVE source.
- May 4, 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=< 1.69.3
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
- GitHub advisory prototype-pollution reproducerproof of concept · demonstrated
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