Directory Traversal in nodeload-nmickuli

Exploitation

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

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Affected versions of nodeload-nmickuli resolve relative file paths, resulting in a directory traversal vulnerability. A malicious actor can use this vulnerability to access files outside of the intended directory root, which may result in the disclosure of private files on the vulnerable system. Example request: Recommendation No patch is available for this vulnerability. It is recommended that the package is only used for local development, and if the functionality is needed for production, a different package is used instead.

Published by the source

1 Sep 2020, 17:33 UTC

Last modified by the source

9 Jan 2023, 05:03 UTC

Source last checked

26 Oct 2026, 12:08 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-wmcq-3wfx-qjx5

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-wmcq-3wfx-qjx5

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

# Patch Next advisory brief: GHSA-wmcq-3wfx-qjx5

Advisory: Directory Traversal in nodeload-nmickuli
IDs: GHSA-wmcq-3wfx-qjx5
Record: https://patchnext.com/advisories/ghsa-wmcq-3wfx-qjx5 (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 response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nodeload-nmickuli: affected every version

## Suggested inspection (read-only)
- `npm ls nodeload-nmickuli --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 nodeload-nmickuli.
- 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-wmcq-3wfx-qjx5 (OSV record GHSA-wmcq-3wfx-qjx5 lists affected ranges: npm nodeload-nmickuli >=0.0.0)
- Verified: https://github.com/advisories/GHSA-wmcq-3wfx-qjx5 (GitHub-reviewed advisory GHSA-wmcq-3wfx-qjx5 lists affected ranges: npm nodeload-nmickuli >=0.0.0)

Commands are suggestions: review each one before running it.