Skip to main content
VulnerabilityPublished Updated

CVE-2025-57353: Runtime · messageformat prototype pollution vulnerability

Affects @messageformat/runtimeSource GCVE Database

0
Compare
Authoritative record:CVE-2025-57353· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 3.0.2 when convenient.

Data as of 29 Oct 2026, 22:51 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 3.0.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade @messageformat/runtime to 3.0.2.

Affected software

ProductAffectedFixed in
npm@messageformat/runtimeAffected
  • >=3.0.1 <3.0.2
  • =3.0.1
Fixed in
  • 3.0.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The Runtime components of messageformat package for Node.js version 3.0.1 contain a prototype pollution vulnerability. Due to insufficient validation of nested message keys during the processing of message data, an attacker can manipulate the prototype chain of JavaScript objects by providing specially crafted input. This can result in the injection of arbitrary properties into the Object.prototype, potentially leading to denial of service conditions or unexpected application behavior. The vulnerability allows attackers to alter the prototype of base objects, impacting all subsequent object instances throughout the application's lifecycle. Version 3.0.2 contains a fix.

References

Community reviews

Loading reviews…