Improper handling of multiline messages in node-irc affects matrix-appservice-ircGHSA-37hr-348p-rmf4
HIGHGHSA-37hr-348p-rmf4 is a high-severity (CVSS 8) CWE-74 vulnerability in matrix-appservice-irc. A fix is available for matrix-appservice-irc — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- 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-37hr-348p-rmf4.
EPSS Exploitation Probability
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
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.
matrix-appservice-ircnpmDescription
matrix-appservice-irc is a Node.js IRC bridge for Matrix. The vulnerability in node-irc allows an attacker to manipulate a Matrix user into executing IRC commands by having them reply to a maliciously crafted message. The vulnerability has been patched in matrix-appservice-irc 0.33.2. Refrain from replying to messages from untrusted participants in IRC-bridged Matrix rooms. There are no known workarounds for this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | matrix-appservice-irc | all versions | 0.33.2npm install matrix-appservice-irc@0.33.2 |
Affected Products
matrix irc bridgematrixDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for matrix-appservice-irc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update matrix-appservice-irc to 0.33.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-37hr-348p-rmf4 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.
Frequently Asked Questions
Is GHSA-37hr-348p-rmf4 in your dependencies?
Find it across npm, including transitive dependencies.