CVE
install-artifact-from-github unverified native artifact loading enables code execution
Only affects install-artifact-from-github 1.6.0 and earlier when the download source is a mirror set via the RE2_DOWNLOAD_MIRROR environment variable. Fixed in 1.7.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.7.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Installs install-artifact-from-github version 1.6.0 or earlier Download source is a mirror set via the RE2_DOWNLOAD_MIRROR environment variable
Summary
The install-artifact-from-github package loads downloaded native artifacts without verifying their integrity, so an attacker who can reach it remotely, without logging in, can supply native code that runs when the artifact is loaded. Exploitation requires user action, and the attacker must control a configured mirror, replace a release asset, or modify unencrypted transport.
Original description
install-artifact-from-github installs prebuilt native artifacts hosted by GitHub without compiling them locally. Prior to 1.7.0, bin/install-from-cache.js downloads a native .node artifact, allows RE2_DOWNLOAD_MIRROR to select a source, follows HTTP redirects including HTTPS-to-HTTP downgrades, and writes the decompressed response to the artifact path without cryptographic integrity verification before writing or loading it. An attacker who controls a configured mirror, replaces a release asset, or can modify plaintext transport can supply native code that executes when the consumer loads the artifact. Version 1.7.0 adds SHA-256 verification for default-GitHub-source downloads when the consuming package publishes an artifactHashes bag; configured mirrors and packages without a bag remain outside that verification.
Who should check
Anyone installing install-artifact-from-github 1.6.0 or earlier to fetch prebuilt native .node artifacts, such as node-re2 consumers
Not fixed by: Upgrading alone does not verify packages that publish no artifactHashes bag.
“bin/install-from-cache.js downloads a prebuilt native addon”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
Installs install-artifact-from-github version 1.6.0 or earlier Download source is a mirror set via the RE2_DOWNLOAD_MIRROR environment variableUpgrade to a fixed version: 1.7.0.
Workaround: Build from source instead of downloading, e.g. via DEVELOPMENT_SKIP_GETTING_ASSET or a .development file
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-73864 (install-artifact-from-github loads downloaded native artifacts without integrity verification), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-73864 (entry last updated 2026-11-18):
Affected:
- uhop install-artifact-from-github: fixed in 1.7.0
Fixed versions: 1.7.0.
Conditions (all must be true for the bug to be hit):
- Installs install-artifact-from-github version 1.6.0 or earlier (source: https://github.com/uhop/install-artifact-from-github/security/advisories/GHSA-88q3-gch3-5396)
- Download source is a mirror set via the RE2_DOWNLOAD_MIRROR environment variable (source: https://github.com/uhop/install-artifact-from-github/security/advisories/GHSA-88q3-gch3-5396)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
Workaround: Build from source instead of downloading, e.g. via DEVELOPMENT_SKIP_GETTING_ASSET or a .development file (source: https://github.com/uhop/install-artifact-from-github/security/advisories/GHSA-88q3-gch3-5396)
CISA KEV: CVE-2026-73864 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-73864 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/uhop/install-artifact-from-github/security/advisories/GHSA-88q3-gch3-5396
- https://github.com/uhop/install-artifact-from-github/commit/1d2d8637556a03f6235e50fe0c238c6dce291633
- https://github.com/uhop/install-artifact-from-github/releases/tag/1.7.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-73864
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-73864"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- uhop install-artifact-from-github
fixed in 1.7.0
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · uhop/install-artifact-from-github · Advisory GHSA-88q3-gch3-5396 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-73864 |
| Record | NVD · CVE-2026-73864 |
| Other links 2 | |
| Repository | GitHub · uhop/install-artifact-from-github · Commit 1d2d8637 |
| Repository | GitHub · uhop/install-artifact-from-github · Release 1.7.0 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-73864
Is CVE-2026-73864 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The package downloads a native addon during install without integrity verification. If the download is redirected to an arbitrary host, the downloaded addon can run code on the installing machine when it is loaded.Source: github.com
Which versions are affected by CVE-2026-73864?
install-artifact-from-github: before 1.7.0.Source: cve.now feed data
Am I affected, and how do I check?
Versions 1.6.0 and earlier are affected when the download source is a mirror set via the RE2_DOWNLOAD_MIRROR environment variable. To check, look at the installed install-artifact-from-github version and whether RE2_DOWNLOAD_MIRROR is set in the environment used for installs.Source: github.com
How do I fix CVE-2026-73864?
Upgrade to 1.7.0, which adds hash-bag verification of the downloaded artifact. If you cannot upgrade yet, build from source instead of downloading, for example via DEVELOPMENT_SKIP_GETTING_ASSET or a .development file.Source: github.com