/

CVE-2026-78637

Severity:

HIGH RISK

(7.3)

Argument Injection (CWE-88) in node-poppler PDF APIs

CVE-2026-78637

Deferred

Vulnerability type

Category:

Argument Injection

CWE:

CWE-74, CWE-88

Impact:

Command execution or unauthorized manipulation of PDF processing

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A high-severity argument injection vulnerability in node-poppler affects PDF helper APIs that process the file_path argument. If an attacker can influence this value, crafted input may be interpreted as additional command-line arguments, potentially altering Poppler operations or enabling unintended command execution.

Affected context

The vulnerability occurs in node-poppler PDF wrapper functions such as pdfInfo, pdfToText, pdfToCairo, pdfToPpm, pdfImages, pdfToHtml, pdfToPs, pdfFonts, pdfDetach, pdfAttach, pdfSeparate, and pdfUnite. It becomes risky when externally influenced file_path values are passed to underlying Poppler commands without sufficient argument boundary enforcement or input trust controls.

Exploit preconditions

  • Attack surface: Applications or services exposing node-poppler PDF processing functionality
  • Required access: Ability to supply or influence the file_path argument, potentially through a remotely reachable application
  • Trigger point: Invocation of an affected PDF helper function
  • Why exploitation is possible: The supplied value may be interpreted as command-line syntax rather than only as a file path

Why this happens

The underlying bug is insufficient separation between untrusted data and command-line arguments. A wrapper that constructs or forwards a process invocation without reliably preserving argument boundaries can allow a caller-controlled file path to introduce additional options or control values. This behavior maps primarily to CWE-88, Argument Injection, and is also related to CWE-74, Injection.

Potential impact

  • An attacker may alter the behavior of PDF conversion or inspection operations.
  • The application could process unintended files or write output to unintended locations.
  • Sensitive data may be exposed through manipulated command options.
  • Under permissive process privileges, crafted input could contribute to arbitrary command execution.
  • Downstream services or generated documents could be affected.

General mitigation guidance

Mitigation generally focuses on preserving strict argument boundaries and

reducing trust in caller-controlled paths.

Common defensive patterns include:

  • Passing process arguments through APIs that represent each argument separately rather than assembling shell command strings.
  • Rejecting option-like values and applying strict allowlists for permitted paths and file types.
  • Resolving paths within controlled directories and preventing traversal or unexpected file access.
  • Using safe-by-default wrapper interfaces that do not permit arbitrary Poppler options.
  • Running PDF processing with minimal filesystem, network, and operating-system privileges.
  • Separating untrusted document processing from sensitive application workloads.

How teams detect issues like this

Organizations can look for this weakness through:

  • Static analysis rules identifying shell command construction or unsafe process-spawn patterns.
  • Code review checks for caller-controlled values passed into command wrappers.
  • Tests using benign option-like and delimiter-containing inputs to verify argument boundaries.
  • Runtime monitoring for unexpected Poppler flags, child processes, file access, or output locations.
  • Policy enforcement requiring structured process APIs and approved input-validation helpers.

Automated code review and software composition analysis tools may help identify

affected wrapper patterns and dependency exposure.

Sources

SourceLink
github.comgithub.com/Fdawgs/node-poppler/
github.comgithub.com/Fdawgs/node-poppler/commit/db6e3f79d3beb20601be7e59669c39811ae3c330
github.comgithub.com/Fdawgs/node-poppler/issues/822
github.comgithub.com/Fdawgs/node-poppler/pull/842
vuldb.comvuldb.com/cve/CVE-2026-78637
vuldb.comvuldb.com/submit/886399
vuldb.comvuldb.com/vuln/394864
vuldb.comvuldb.com/vuln/394864/cti

Frequently asked

questions

It may be remotely exploitable when a network-accessible application passes

attacker-controlled input to an affected node-poppler function. Remote

reachability depends on how the application exposes and validates file_path.

The attacker generally needs a way to influence the file path or related PDF

processing request. Authentication requirements depend on the surrounding

application and its access controls.

Preserve argument boundaries by using structured process APIs, reject

unexpected option-like input, and restrict file paths to controlled,

allowlisted locations.

Treat all externally supplied paths as untrusted, avoid shell-style command

construction, apply least privilege to document-processing workers, and use

code review and automated analysis to detect unsafe process invocation.

Find out what's already
exploitable in your codebase.