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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-xfqm-j7pc-xrfc?

O3 pinpoints whether GHSA-xfqm-j7pc-xrfc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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 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

GHSA-xfqm-j7pc-xrfc

GHSA-xfqm-j7pc-xrfc is a CWE-1321 vulnerability in messageformat. O3 Security confirms whether GHSA-xfqm-j7pc-xrfc is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

messageformat has a prototype pollution vulnerability

Also known asCVE-2025-57349

Published

Sep 24, 2025

Updated

Sep 25, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

messageformatnpm

338Kdownloads / 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

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for messageformat. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-xfqm-j7pc-xrfc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-xfqm-j7pc-xrfc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-xfqm-j7pc-xrfc across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works