Dev.to Security 🔐 Cybersecurity 👁 0 📖 3 min read

CVE-2026-73864: CVE-2026-73864: Unverified Native Artifact Download Leading to Remote Code Execution in…

CVE-2026-73864: Unverified Native Artifact Download Leading to Remote Code Execution in install-artifact-from-github Vulnerability ID: CVE-2026-73864 CVSS Score: 7.5 Published: 2026-11-18 CVE-2026-73864 is a CWE-494

CVE-2026-73864: Unverified Native Artifact Download Leading to Remote Code Execution in install-artifact-from-github

Vulnerability ID: CVE-2026-73864
CVSS Score: 7.5
Published: 2026-11-18

CVE-2026-73864 is a CWE-494 (Download of Code Without Integrity Check) vulnerability in the Node.js package install-artifact-from-github prior to version 1.7.0. The tool downloads precompiled native Node.js C/C++ addons (.node binaries) from GitHub Releases or configurable mirrors and writes them directly to disk without verifying cryptographic checksums or signatures. Furthermore, its HTTP client follows cross-protocol redirects from HTTPS to plaintext HTTP. When the consuming application loads the downloaded addon via require(), the unverified native binary executes immediately within the Node.js process, permitting arbitrary native code execution if an attacker compromises a GitHub release asset, poisons a configured mirror, or intercepts downgraded network traffic.

TL;DR

Versions of install-artifact-from-github prior to 1.7.0 download and load prebuilt native Node.js (.node) binaries without cryptographic integrity verification, enabling arbitrary native code execution via asset tampering, mirror poisoning, or network interception.

⚠️ Exploit Status: POC

Technical Details

  • CVE ID: CVE-2026-73864 (GHSA-88q3-gch3-5396)
  • Weakness Class: CWE-494: Download of Code Without Integrity Check
  • CVSS v3.1 Score: 7.5 High (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H)
  • Affected Component: install-artifact-from-github (< 1.7.0) - bin/install-from-cache.js
  • Attack Vector: Network (GitHub Release Asset Tampering, Mirror Poisoning, or HTTPS-to-HTTP MitM)
  • Security Impact: Arbitrary Native Code Execution (RCE) via unverified .node shared library loading
  • Patched Version: 1.7.0 (Commit 1d2d8637556a03f6235e50fe0c238c6dce291633)
  • CISA KEV Status: Not Listed

Affected Systems

  • install-artifact-from-github (npm package) versions < 1.7.0
  • Downstream Node.js applications and packages consuming prebuilt native addons via install-artifact-from-github < 1.7.0 (including vulnerable configurations of node-re2)
  • install-artifact-from-github: < 1.7.0 (1.0.0 - 1.6.0) (Fixed in: 1.7.0)

Code Analysis

Commit: 1d2d863

Implemented SHA-256 artifact integrity verification using an artifactHashes bag in package.json, added bin/hash-github-cache.js generator tool, and introduced --force-build / DOWNLOAD_FORCE_BUILD options.

import {createHash} from 'node:crypto';

const slot = `${platform}-${platformArch}-${abiSlot}`;
const isDefaultSource = !mirrorHost && !process.env[mirrorEnvVar];
let artifactHashes = null;

const verifyArtifact = data => {
  if (!isDefaultSource || !artifactHashes) return true;
  const expected = artifactHashes[slot],
    actual = 'sha256:' + createHash('sha256').update(data).digest('hex');
  if (expected && expected === actual) return true;
  console.log(`Integrity check failed for ${slot}: building from sources ...`);
  return false;
};

Mitigation Strategies

  • Embed immutable SHA-256 checksums (artifactHashes) of precompiled native binaries inside the npm-published package.json to establish the npm registry as the root of trust.
  • Enforce local source compilation in high-assurance CI/CD environments using DOWNLOAD_FORCE_BUILD=1 or package-specific force-build variables (e.g., RE2_FORCE_BUILD=1).
  • Restrict and audit the use of custom download mirror environment variables (e.g., RE2_DOWNLOAD_MIRROR, DOWNLOAD_MIRROR), as mirror overrides bypass the default-source SHA-256 verification gate.

Remediation Steps:

  1. Upgrade install-artifact-from-github to version 1.7.0 or later via npm install install-artifact-from-github@^1.7.0.
  2. For package maintainers: run npx hash-github-cache --write prior to npm publish (or configure it in the prepublishOnly npm script) to populate the artifactHashes map in package.json.
  3. For downstream consumers: update dependent packages (such as node-re2) to releases that incorporate install-artifact-from-github >= 1.7.0 and include populated artifactHashes.
  4. Where immediate patching is not feasible, set DOWNLOAD_FORCE_BUILD=1 (or pass --force-build) or compile the native addon locally from source using node-gyp rebuild.

References

Read the full report for CVE-2026-73864 on our website for more details including interactive diagrams and full exploit analysis.

📰 Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.