Skip to content

← Actionable
Unratedamended

Downloads Resources over HTTP in libxl

CVE-2016-10585GHSA-7vrq-vg6p-32fw

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 libxl

    Affected
    <= 0.4.5
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2016-10585: 1.73% estimated exploitation activity in the next 30 days; percentile 77.56 (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 libxl 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 libxl. Recommendation The module author recommends installing the bindings using a pinned and verified version of SDK instead of the automated download. More information is available in the modules README.

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

    Amended from ghsa record GHSA-7vrq-vg6p-32fw

  2. Revision 1 · created ·

    Published from osv record GHSA-7vrq-vg6p-32fw

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-10585

Advisory: Downloads Resources over HTTP in libxl
IDs: CVE-2016-10585, GHSA-7vrq-vg6p-32fw
Record: https://patchnext.com/advisories/cve-2016-10585 (revision 2, source checked 26 Oct 2026, 12:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
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 libxl: affected <= 0.4.5

## Suggested inspection (read-only)
- `npm ls libxl --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 libxl.
- 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-7vrq-vg6p-32fw (OSV record GHSA-7vrq-vg6p-32fw lists affected ranges: npm libxl >=0 <=0.4.5)
- Verified: https://github.com/advisories/GHSA-7vrq-vg6p-32fw (GitHub-reviewed advisory GHSA-7vrq-vg6p-32fw lists affected ranges: npm libxl >=0 <=0.4.5)

Commands are suggestions: review each one before running it.

Loading voting…