How severe is GHSA-6375-pg5j-8wph?

GHSA-6375-pg5j-8wph has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-6375-pg5j-8wph?

GHSA-6375-pg5j-8wph affects the following packages: @rocket.chat/message-parser (npm). Ecosystems affected: npm.

How do I fix GHSA-6375-pg5j-8wph?

Update @rocket.chat/message-parser to 0.31.30 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6375-pg5j-8wph is resolved across your whole dependency graph.

How do I detect GHSA-6375-pg5j-8wph in my npm dependencies?

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

How do I mitigate GHSA-6375-pg5j-8wph 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-6375-pg5j-8wph actively exploited in the wild?

No public exploit code has been indexed for GHSA-6375-pg5j-8wph 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-6375-pg5j-8wph?

GHSA-6375-pg5j-8wph has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 49th 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.

When was GHSA-6375-pg5j-8wph published, and has it been updated?

GHSA-6375-pg5j-8wph was published on September 25, 2024 and was last updated on September 26, 2024. 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

HIGH severity

Denial of service in rocket chat message parserGHSA-6375-pg5j-8wph

HIGHFix: RocketChat/Rocket.Chat#33227

GHSA-6375-pg5j-8wph is a high-severity (CVSS 7.5) vulnerability in @rocket.chat/message-parser. A fix is available for @rocket.chat/message-parser — see the affected versions and patch details below.

Also known asCVE-2024-46935

Published

Sep 25, 2024

Updated

Sep 26, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

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-6375-pg5j-8wph.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs49th percentile — riskier than 49% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

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.

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

@rocket.chat/message-parsernpm

2Kdownloads / week

Description

Rocket.Chat 6.12.0, 6.11.2, 6.10.5, 6.9.6, 6.8.6, 6.7.8, and earlier is vulnerable to denial of service (DoS). Attackers who craft messages with specific characters may crash the workspace due to an issue in the message parser.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@rocket.chat/message-parser`	all versions	0.31.30`npm install @rocket.chat/message-parser@0.31.30`

Affected Products

1 product · 12 configurations

Application

rocket.chatrocket.chat

≥ 6.11.0 && < 6.11.3

1 version

6.12.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @rocket.chat/message-parser, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @rocket.chat/message-parser to 0.31.30 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6375-pg5j-8wph 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

O3 Security · Impact-Aware SCA

Is GHSA-6375-pg5j-8wph in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works