jdf-sass downloads Resources over HTTP

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-10595: 1.61% estimated exploitation activity in the next 30 days; percentile 75.91 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Affected versions of jdf-sass 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 jdf-sass. Recommendation No patch is currently available for this vulnerability. The best mitigation is currently to avoid using this package, using a different package if available. Alternatively, the risk of exploitation can be reduced by ensuring that this package is not installed while connected to a public network. If the package is installed on a private network, the only people who can exploit this vulnerability are those who have compromised your network or those who have privileged access to your ISP, such as Nation State Actors or Rogue ISP Employees.

Published by the source

18 Feb 2019, 23:34 UTC

Last modified by the source

8 Nov 2023, 03:58 UTC

Source last checked

26 Oct 2026, 12:26 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-8cc8-8vvx-fhgw

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-8cc8-8vvx-fhgw

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

# Patch Next advisory brief: CVE-2016-10595

Advisory: jdf-sass downloads Resources over HTTP
IDs: CVE-2016-10595, GHSA-8cc8-8vvx-fhgw
Record: https://patchnext.com/advisories/cve-2016-10595 (revision 2, source checked 26 Oct 2026, 12:26 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 jdf-sass: affected <= 1.0.18

## Suggested inspection (read-only)
- `npm ls jdf-sass --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 jdf-sass.
- 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-8cc8-8vvx-fhgw (OSV record GHSA-8cc8-8vvx-fhgw lists affected ranges: npm jdf-sass >=0 <=1.0.18)
- Verified: https://github.com/advisories/GHSA-8cc8-8vvx-fhgw (GitHub-reviewed advisory GHSA-8cc8-8vvx-fhgw lists affected ranges: npm jdf-sass >=0 <=1.0.18)

Commands are suggestions: review each one before running it.