NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
💧
💧 Hex
Not in CISA KEV
HIGH severity

CVE-2017-1000052 — plug

HIGH

CVE-2017-1000052 is a high-severity (CVSS 7.8) CWE-74 vulnerability in plug. A fix is available for plug — see the affected versions and patch details below.

Null Byte Injection in Plug.Static

Also known asGHSA-2q6v-32mr-8p8x
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk
0.00%0.31%0.62%0.92%0.2%0.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected
💧plug💧plug💧plug💧plug

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Hex packages — download data is not available via public APIs for these ecosystems.

Description

Plug.Static is used for serving static assets, and is vulnerable to null byte injection. If file upload functionality is provided, this can allow users to bypass filetype restrictions. We recommend all applications that provide file upload functionality and serve those uploaded files locally with Plug.Static to upgrade immediately or include the fix below. If uploaded files are rather stored and served from S3 or any other cloud storage, you are not affected.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
💧Hexplugall versions1.0.4mix deps.update plug
💧Hexplug≥ 1.1.0&&< 1.1.71.1.7mix deps.update plug
💧Hexplug≥ 1.2.0&&< 1.2.31.2.3mix deps.update plug
💧Hexplug≥ 1.3.0&&< 1.3.21.3.2mix deps.update plug

Affected Products

1 product · 4 configurations
Application
plugplug_project
≥ 1.3.0 && < 1.3.2
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for plug, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update plug to 1.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-1000052 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Plug.Static is used for serving static assets, and is vulnerable to null byte injection. If file upload functionality is provided, this can allow users to bypass filetype restrictions. We recommend all applications that provide file upload functionality and serve those uploaded files locally with Plug.Static to upgrade immediately or include the fix below. If uploaded files are rather stored and served from S3 or any other cloud storage, you are not affected.
O3 Security · Impact-Aware SCA

Is CVE-2017-1000052 in your dependencies?

Find it across Hex, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2017-1000052: plug — Fixed in 1.0.4