Application crashes via prototype-polluting message keys
Published Sep 24, 2025 · Updated Sep 24, 2025
Prototype pollution in messageformat before 2.3.0 allows remote attackers to alter Object.prototype through crafted message keys. During nested message registration, the package traverses attacker-controlled key paths without rejecting proto, so an assignment writes into the global prototype chain. Exploitation requires an application to process untrusted message definitions and can crash the application or trigger behavior that depends on polluted properties.
Summary
What happened
Prototype pollution in messageformat before 2.3.0 allows remote attackers to alter Object.prototype through crafted message keys. During nested message registration, the package traverses attacker-controlled key paths without rejecting proto, so an assignment writes into the global prototype chain. Exploitation requires an application to process untrusted message definitions and can crash the application or trigger behavior that depends on polluted properties.
The record
- CVE
- CVE-2025-57349
- Published
- Sep 24, 2025
- Updated
- Sep 24, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 24, 2025CVE publishedPublication date reported by the CVE source.
- Sep 24, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
No public exploit references are available in this record.
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