Pkg Local Privilege Escalation

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.6 · CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N

EPSS

• CVE-2024-24828: 0.23% estimated exploitation activity in the next 30 days; percentile 14.25 (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.

Impact Any native code packages built by pkg are written to a hardcoded directory. On unix systems, this is /tmp/pkg/ which is a shared directory for all users on the same local system. There is no uniqueness to the package names within this directory, they are predictable. An attacker who has access to the same local system has the ability to replace the genuine executables in the shared directory with malicious executables of the same name. A user may then run the malicious executable without realising it has been modified. Patches This package is deprecated. Therefore, there will not be a patch provided for this vulnerability. Recommended Action: To check if your executable build by pkg depends on native code and is vulnerable, run the executable and check if /tmp/pkg/ was created. Users should transition to actively maintained alternatives. We would recommend investigating Node.js 21’s support for single executable applications. Workarounds Given the decision to deprecate the pkg…

Published by the source

9 Feb 2024, 15:20 UTC

Last modified by the source

10 Sep 2026, 03:50 UTC

Source last checked

26 Oct 2026, 12:30 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-22r3-9w55-cj54

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-22r3-9w55-cj54

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

# Patch Next advisory brief: CVE-2024-24828

Advisory: Pkg Local Privilege Escalation
IDs: CVE-2024-24828, GHSA-22r3-9w55-cj54
Record: https://patchnext.com/advisories/cve-2024-24828 (revision 2, source checked 26 Oct 2026, 12:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.6)
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 pkg: affected <= 5.8.1

## Suggested inspection (read-only)
- `npm ls pkg --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 pkg.
- 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-22r3-9w55-cj54 (OSV record GHSA-22r3-9w55-cj54 lists affected ranges: npm pkg >=0 <=5.8.1)
- Verified: https://github.com/advisories/GHSA-22r3-9w55-cj54 (GitHub-reviewed advisory GHSA-22r3-9w55-cj54 lists affected ranges: npm pkg >=0 <=5.8.1)

Commands are suggestions: review each one before running it.