Skip to content

← Actionable
High, CVSS 8.1amended

closure-util downloads Resources over HTTP

CVE-2016-10583GHSA-2hpj-g53m-9gj6

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • npm closure-util

    Affected
    <= 2.0.0-beta.1
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2016-10583: 2.51% estimated exploitation activity in the next 30 days; percentile 84.76 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Affected versions of closure-util insecurely download an executable over an unencrypted HTTP connection. In scenarios where an attacker has a privileged network position, it is possible to intercept the response and replace the executable with a malicious one, resulting in code execution on the system running closure-util. Recommendation To mitigate this issue: 1. Install the package using npm's --ignore-scripts flag. 2. Navigate to the package directory, and open default-config.json in a text editor 3. Change the download URLs in the compilerurl and libraryurl to https equivalents 4. run npm i in the package directory.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-2hpj-g53m-9gj6

  2. Revision 1 · created ·

    Published from osv record GHSA-2hpj-g53m-9gj6

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2016-10583

Advisory: closure-util downloads Resources over HTTP
IDs: CVE-2016-10583, GHSA-2hpj-g53m-9gj6
Record: https://patchnext.com/advisories/cve-2016-10583 (revision 2, source checked 26 Oct 2026, 12:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm closure-util: affected <= 2.0.0-beta.1

## Suggested inspection (read-only)
- `npm ls closure-util --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on closure-util.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-2hpj-g53m-9gj6 (OSV record GHSA-2hpj-g53m-9gj6 lists affected ranges: npm closure-util >=0 <=2.0.0-beta.1)
- Verified: https://github.com/advisories/GHSA-2hpj-g53m-9gj6 (GitHub-reviewed advisory GHSA-2hpj-g53m-9gj6 lists affected ranges: npm closure-util >=0 <=2.0.0-beta.1)

Commands are suggestions: review each one before running it.

Loading voting…