How severe is GHSA-rcrx-fpjp-mfrw?

GHSA-rcrx-fpjp-mfrw has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-rcrx-fpjp-mfrw?

GHSA-rcrx-fpjp-mfrw affects the following packages: muhammara (npm), hummus (npm). Ecosystems affected: npm.

How do I fix GHSA-rcrx-fpjp-mfrw?

Update muhammara to 2.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rcrx-fpjp-mfrw is resolved across your whole dependency graph.

How do I detect GHSA-rcrx-fpjp-mfrw in my npm dependencies?

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

How do I mitigate GHSA-rcrx-fpjp-mfrw 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-rcrx-fpjp-mfrw actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-rcrx-fpjp-mfrw, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-rcrx-fpjp-mfrw?

GHSA-rcrx-fpjp-mfrw has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 60th 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-rcrx-fpjp-mfrw?

GHSA-rcrx-fpjp-mfrw is classified as CWE-690 (CWE-690), NULL Pointer Dereference (CWE-476). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-rcrx-fpjp-mfrw published, and has it been updated?

GHSA-rcrx-fpjp-mfrw was published on November 2, 2022 and was last updated on November 8, 2023. 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

Unchecked Return Value to NULL Pointer Dereference in PDFDocumentHandler.cppGHSA-rcrx-fpjp-mfrw

HIGHFix: julianhille/MuhammaraJS#194

GHSA-rcrx-fpjp-mfrw is a high-severity (CVSS 7.5) CWE-690 vulnerability in muhammara. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for muhammara — see the affected versions and patch details below.

Also known asCVE-2022-39381

Published

Nov 2, 2022

Updated

Nov 8, 2023

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for GHSA-rcrx-fpjp-mfrw.

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs60th percentile — riskier than 60% 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

2 pkgs affected

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

muhammaranpm

57Kdownloads / week

hummusnpm

5Kdownloads / week

Description

Impact

The package muhammara before 2.6.0; all versions of package hummus are vulnerable to Denial of Service (DoS) when supplied with a maliciously crafted PDF file to be appended to another.

Patches

It has been patched in 2.6.0 for muhammara and not at all for hummus

Workarounds

Do not process files from untrusted sources

References

PR: https://github.com/julianhille/MuhammaraJS/pull/194 Issue: https://github.com/julianhille/MuhammaraJS/issues/191 Issue in hummus: https://github.com/galkahana/HummusJS/issues/293

Outline differences to https://nvd.nist.gov/vuln/detail/CVE-2022-25892

The difference is one is in src/deps/PDFWriter/PDFParser.cpp and the other is PDFDocumentHandler.cpp both is a null pointer but for different cases These are totally diffent issues, one is in reading a pdf the other is in appendending a maliciously crafted one. The function calls are different the versions in which they are solved are diffent.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`muhammara`	all versions	2.6.0`npm install muhammara@2.6.0`
📦npm	`hummus`	all versions	1.0.111`npm install hummus@1.0.111`

Affected Products

2 products · 2 configurations

Application

muhammarajsmuhammarajs_project

≤ 2.6.0

range

Application

hummusjspdfhummus

< 1.0.111

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Muhammara is a node module with c/cpp bindings to modify PDF with js for…

github.comNVDNov 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for muhammara, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update muhammara to 2.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rcrx-fpjp-mfrw 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

### Impact The package muhammara before 2.6.0; all versions of package hummus are vulnerable to Denial of Service (DoS) when supplied with a maliciously crafted PDF file to be appended to another. ### Patches It has been patched in 2.6.0 for muhammara and not at all for hummus ### Workarounds Do not process files from untrusted sources ### References PR: https://github.com/julianhille/MuhammaraJS/pull/194 Issue: https://github.com/julianhille/MuhammaraJS/issues/191 Issue in hummus: https://github.com/galkahana/HummusJS/issues/293 ### Outline differences to https://nvd.nist.gov/vuln/detail/