Unratedamended

Path Traversal in m-server

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (m-server 1.4.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

npm m-server
Affected
< 1.4.2
Fixed in
1.4.2

Sources

Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-vc6r-4x6g-mmqc lists affected ranges: npm m-server >=0 <1.4.2 (fixed)
VerifiedObserved 24 Oct 2026, 04:13 UTCStructured OSV record; GitHub-reviewed advisory.
GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-vc6r-4x6g-mmqc lists affected ranges: npm m-server >=0 <1.4.2
VerifiedObserved 26 Oct 2026, 12:06 UTCStructured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation

Exploitation: No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS: not scored
EPSS: No dated EPSS signal available.

Source description

As published by the source; long descriptions are shortened.

Versions of m-server before 1.4.2 are vulnerable to path traversal allowing a remote attacker to display content of arbitrary files from the server. Recommendation Update to version 1.4.2 or later.

Dates and revisions

Published by the source: 11 Jun 2019, 16:16 UTC
Last modified by the source: 9 Jan 2023, 05:01 UTC
Source last checked: 26 Oct 2026, 12:06 UTC

Revision 2 · amended · 26 Oct 2026
Amended from ghsa record GHSA-vc6r-4x6g-mmqc
Revision 1 · created · 24 Oct 2026
Published from osv record GHSA-vc6r-4x6g-mmqc

Agent brief

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

# Patch Next advisory brief: GHSA-vc6r-4x6g-mmqc

Advisory: Path Traversal in m-server
IDs: GHSA-vc6r-4x6g-mmqc
Record: https://patchnext.com/advisories/ghsa-vc6r-4x6g-mmqc (revision 2, source checked 26 Oct 2026, 12:06 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 fix available; fixed versions by package: m-server 1.4.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm m-server: affected < 1.4.2; fixed in 1.4.2

## Suggested inspection (read-only)
- `npm ls m-server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on m-server.
- 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-vc6r-4x6g-mmqc (OSV record GHSA-vc6r-4x6g-mmqc lists affected ranges: npm m-server >=0 <1.4.2 (fixed))
- Verified: https://github.com/advisories/GHSA-vc6r-4x6g-mmqc (GitHub-reviewed advisory GHSA-vc6r-4x6g-mmqc lists affected ranges: npm m-server >=0 <1.4.2)

Commands are suggestions: review each one before running it.

Loading voting…