How severe is GHSA-xfqm-j7pc-xrfc?

No CVSS score has been assigned to GHSA-xfqm-j7pc-xrfc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xfqm-j7pc-xrfc?

GHSA-xfqm-j7pc-xrfc affects the following packages: messageformat (npm). Ecosystems affected: npm.

How do I fix GHSA-xfqm-j7pc-xrfc?

Update messageformat to 3.0.0-beta.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xfqm-j7pc-xrfc is resolved across your whole dependency graph.

How do I detect GHSA-xfqm-j7pc-xrfc in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for messageformat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-xfqm-j7pc-xrfc if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-xfqm-j7pc-xrfc actively exploited in the wild?

No public exploit code has been indexed for GHSA-xfqm-j7pc-xrfc yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-xfqm-j7pc-xrfc?

GHSA-xfqm-j7pc-xrfc has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 35th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-xfqm-j7pc-xrfc?

GHSA-xfqm-j7pc-xrfc is classified as CWE-1321 (CWE-1321). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-xfqm-j7pc-xrfc published, and has it been updated?

GHSA-xfqm-j7pc-xrfc was published on September 24, 2025 and was last updated on September 25, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

messageformat has a prototype pollution vulnerabilityGHSA-xfqm-j7pc-xrfc

GHSA-xfqm-j7pc-xrfc is a CWE-1321 vulnerability in messageformat. A fix is available for messageformat — see the affected versions and patch details below.

Also known asCVE-2025-57349

Published

Sep 24, 2025

Updated

Sep 25, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-xfqm-j7pc-xrfc.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs35th percentile — riskier than 35% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

182other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

messageformatnpm

633Kdownloads / week

Description

The messageformat package, an implementation of the Unicode MessageFormat 2 specification for JavaScript, is vulnerable to prototype pollution due to improper handling of message key paths in versions prior to 2.3.0. The flaw arises when processing nested message keys containing special characters (e.g., proto ), which can lead to unintended modification of the JavaScript Object prototype. This vulnerability may allow a remote attacker to inject properties into the global object prototype via specially crafted message input, potentially causing denial of service or other undefined behaviors in applications using the affected component.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`messageformat`	all versions	3.0.0-beta.0`npm install messageformat@3.0.0-beta.0`

Affected Products

1 product · 1 configurations

Application

messageformatopenjsf

< 2.3.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for messageformat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update messageformat to 3.0.0-beta.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xfqm-j7pc-xrfc is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

The messageformat package, an implementation of the Unicode MessageFormat 2 specification for JavaScript, is vulnerable to prototype pollution due to improper handling of message key paths in versions prior to 2.3.0. The flaw arises when processing nested message keys containing special characters (e.g., __proto__ ), which can lead to unintended modification of the JavaScript Object prototype. This vulnerability may allow a remote attacker to inject properties into the global object prototype via specially crafted message input, potentially causing denial of service or other undefined behavior

O3 Security · Impact-Aware SCA

Is GHSA-xfqm-j7pc-xrfc in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works