CVE-2017-16156

HIGHNVD 7.5

7.5

myprolyz is a static file server. myprolyz is vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing "../" in the url.

CVSS v3: 7.5
EG Score: —
EPSS: 67.6%
KEV: Not listed

Published

June 7, 2018

Last Modified

November 21, 2024

References (4)

support@hackeronehttps://github.com/JacksonGL/NPM-Vuln-PoC/tree/master/directory-traversal/myprolyz
support@hackeronehttps://nodesecurity.io/advisories/386
af854a3a-2127-422b-91ae-364da2661108https://github.com/JacksonGL/NPM-Vuln-PoC/tree/master/directory-traversal/myprolyz
af854a3a-2127-422b-91ae-364da2661108https://nodesecurity.io/advisories/386

Affected Packages

(1 across 1 ecosystem)

npm(1)

Package	Vulnerable range	Fixed in	Dependents
myprolyz	—	—	—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-22Path Traversal

Data Freshness Timeline

(refreshed 6× in last 7d / 6× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(5)

What is CVE-2017-16156?

CVE-2017-16156 is a high vulnerability published on June 7, 2018. myprolyz is a static file server. myprolyz is vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing "../" in the url.

When was CVE-2017-16156 disclosed?

CVE-2017-16156 was first published in the National Vulnerability Database on June 7, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2017-16156 actively exploited?

CVE-2017-16156 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 67.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2017-16156?

CVE-2017-16156 has a CVSS v3 base score of 7.5 (NVD).

How do I remediate CVE-2017-16156?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-16156, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-16156

Explore →

Is Your Infrastructure Affected by CVE-2017-16156?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs