Skip to content

← Actionable
High, CVSS 7.5amended

Unchecked Return Value to NULL Pointer Dereference in PDFDocumentHandler.cpp

CVE-2022-39381GHSA-rcrx-fpjp-mfrw

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (hummus 1.0.111; muhammara 2.6.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • npm hummus

    Affected
    < 1.0.111
    Fixed in
    1.0.111
  • npm muhammara

    Affected
    < 2.6.0
    Fixed in
    2.6.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2022-39381: 0.89% estimated exploitation activity in the next 30 days; percentile 59.55 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-rcrx-fpjp-mfrw

  2. Revision 1 · created ·

    Published from osv record GHSA-rcrx-fpjp-mfrw

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-39381

Advisory: Unchecked Return Value to NULL Pointer Dereference in PDFDocumentHandler.cpp
IDs: CVE-2022-39381, GHSA-rcrx-fpjp-mfrw
Record: https://patchnext.com/advisories/cve-2022-39381 (revision 2, source checked 26 Oct 2026, 12:21 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: hummus 1.0.111; muhammara 2.6.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm hummus: affected < 1.0.111; fixed in 1.0.111
- npm muhammara: affected < 2.6.0; fixed in 2.6.0

## Suggested inspection (read-only)
- `npm ls hummus --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls muhammara --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on hummus, muhammara.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-rcrx-fpjp-mfrw (OSV record GHSA-rcrx-fpjp-mfrw lists affected ranges: npm muhammara >=0 =0 <1.0.111 (fixed))
- Verified: https://github.com/advisories/GHSA-rcrx-fpjp-mfrw (GitHub-reviewed advisory GHSA-rcrx-fpjp-mfrw lists affected ranges: npm muhammara >=0 =0 <1.0.111)

Commands are suggestions: review each one before running it.

Loading voting…