Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Downloads Resources over HTTP in js-given

CVE-2016-10638GHSA-rqwh-c535-j9hw

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (js-given 0.0.18), redeploy, then verify what is actually installed.

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.

Add to your agent

Affected packages

  • npm js-given

    Affected
    < 0.0.18
    Fixed in
    0.0.18

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2016-10638: 1.66% estimated exploitation activity in the next 30 days; percentile 76.62 (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 js-given 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 js-given. Recommendation Update to version 0.0.18 or later.

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

    Amended from ghsa record GHSA-rqwh-c535-j9hw

  2. Revision 1 · created ·

    Published from osv record GHSA-rqwh-c535-j9hw

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

Advisory: Downloads Resources over HTTP in js-given
IDs: CVE-2016-10638, GHSA-rqwh-c535-j9hw
Record: https://patchnext.com/advisories/cve-2016-10638 (revision 2, source checked 26 Oct 2026, 12:08 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 fix available; fixed versions by package: js-given 0.0.18. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm js-given: affected < 0.0.18; fixed in 0.0.18

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on js-given.
- 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-rqwh-c535-j9hw (OSV record GHSA-rqwh-c535-j9hw lists affected ranges: npm js-given >=0 <0.0.18 (fixed))
- Verified: https://github.com/advisories/GHSA-rqwh-c535-j9hw (GitHub-reviewed advisory GHSA-rqwh-c535-j9hw lists affected ranges: npm js-given >=0 <0.0.18)

Commands are suggestions: review each one before running it.

Loading voting…