CVE-2016-10591: Prince is a Node API for executing XML/HTML to PDF renderer PrinceXML via prince(1) CLI

Q: How do I fix CVE-2016-10591?

prince: upgrade to 1.4.6. Exact commands for each OS are on this page.

Q: Is CVE-2016-10591 being exploited?

CVE-2016-10591 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2016-10591 affect?

CVE-2016-10591 affects prince. Severity is high (CVSS 8.1). Prince is a Node API for executing XML/HTML to PDF renderer PrinceXML via prince(1) CLI. prince downloads zipped resources over HTTP, which leaves it vulnerable to MITM attacks. It may be possible to cause remote code execution (RCE) by swa

Q: How urgent is CVE-2016-10591?

Priority 53/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 8.1REMOTEUPGRADE

CVE-2016-10591 is a high-severity flaw (CVSS 8.1) affecting prince. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Prince is a Node API for executing XML/HTML to PDF renderer PrinceXML via prince(1) CLI. prince downloads zipped resources over HTTP, which leaves it vulnerable to MITM attacks. It may be possible to cause remote code execution (RCE) by swapping out the requested tarball with an attacker controlled tarball if the attacker is on the network or positioned in between the user and the remote server.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	1.7% (top 22%)
CISA exploited list	No
Weakness	CWE-311, CWE-310
Published	2018-05-29
Last modified	2026-06-17

Publisher (CNA): HackerOne · Vendor: prince project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-05-29 20:29 UTCPublished CVE record published
2026-06-17 00:39 UTCUpdated Record last modified

prince project prince UPGRADE

Affected: >= 1.4.4 and < 1.4.6

Fixed in: 1.4.6

Safe to downgrade to: a release before 1.4.4

1. Check installed version

npm ls prince

2. UPGRADE to 1.4.6

npm install prince@">=1.4.6"

3. If no update is available yet, DOWNGRADE to a release before 1.4.4

npm view prince versions npm install prince@"<1.4.4"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2016-10591?

prince: upgrade to 1.4.6. Exact commands for each OS are on this page.

Is CVE-2016-10591 being exploited?

CVE-2016-10591 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2016-10591 affect?

CVE-2016-10591 affects prince. Severity is high (CVSS 8.1). Prince is a Node API for executing XML/HTML to PDF renderer PrinceXML via prince(1) CLI. prince downloads zipped resources over HTTP, which leaves it vulnerable to MITM attacks. It may be possible to cause remote code execution (RCE) by swa

How urgent is CVE-2016-10591?

Priority 53/100. High severity; Remotely exploitable, no login, no user action

References

← Back to latest CVEs