CVE-2017-16127: The module pandora-doomsday infects other modules

Q: How do I fix CVE-2017-16127?

pandora-doomsday: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2017-16127 being exploited?

CVE-2017-16127 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-2017-16127 affect?

CVE-2017-16127 affects pandora-doomsday. Severity is critical (CVSS 9.8). The module pandora-doomsday infects other modules. It's since been unpublished from the registry.

Q: How urgent is CVE-2017-16127?

Priority 58/100. Critical severity; Remotely exploitable, no login, no user action

This month

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2017-16127 is a critical-severity flaw (CVSS 9.8) affecting pandora-doomsday. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The module pandora-doomsday infects other modules. It's since been unpublished from the registry.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.4% (top 27%)
CISA exploited list	No
Weakness	CWE-509, CWE-276
Published	2018-06-07
Last modified	2026-06-17

Publisher (CNA): HackerOne · Vendor: pandora-doomsday project

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

Am I affected?

Timeline

2018-06-07 02:29 UTCPublished CVE record published
2026-06-17 01:08 UTCUpdated Record last modified

pandora-doomsday project pandora-doomsday DOWNGRADE

Affected: 0.0.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.0.1

1. Check installed version

npm ls pandora-doomsday

2. No fixed release: DOWNGRADE to a release before 0.0.1

npm view pandora-doomsday versions npm install pandora-doomsday@"<0.0.1"

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-2017-16127?

pandora-doomsday: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-16127 being exploited?

CVE-2017-16127 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-2017-16127 affect?

CVE-2017-16127 affects pandora-doomsday. Severity is critical (CVSS 9.8). The module pandora-doomsday infects other modules. It's since been unpublished from the registry.

How urgent is CVE-2017-16127?

Priority 58/100. Critical severity; Remotely exploitable, no login, no user action

References

← Back to latest CVEs