GHSA-rcrx-fpjp-mfrw
HIGHGHSA-rcrx-fpjp-mfrw is a high-severity (CVSS 7.5) CWE-690 vulnerability in muhammara. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-rcrx-fpjp-mfrw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Unchecked Return Value to NULL Pointer Dereference in PDFDocumentHandler.cpp
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
muhammaranpmhummusnpmDescription
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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | muhammara | all versions | 2.6.0 |
| 📦npm | hummus | all versions | 1.0.111 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for muhammara. 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 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
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-rcrx-fpjp-mfrw 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-rcrx-fpjp-mfrw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-rcrx-fpjp-mfrw in your dependencies?
O3 detects GHSA-rcrx-fpjp-mfrw across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.