Path Traversal in socket.io-file

Exploitation

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

CVSS

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

EPSS

• CVE-2020-15779: 1.58% estimated exploitation activity in the next 30 days; percentile 75.55 (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.

All versions of socket.io-file are vulnerable to Path Traversal. The package fails to sanitize user input and uses it to generate the file upload paths. The socket.io-file::createFile message contains a name option that is passed directly to path.join(). It is possible to upload files to arbitrary folders on the server by sending relative paths on the name value, such as ../../test.js. The uploadDir and rename options can be used to define the file upload path.

Published by the source

7 Jul 2020, 19:24 UTC

Last modified by the source

4 May 2026, 08:45 UTC

Source last checked

26 Oct 2026, 12:08 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-9h4g-27m8-qjrg

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-9h4g-27m8-qjrg

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

# Patch Next advisory brief: CVE-2020-15779

Advisory: Path Traversal in socket.io-file
IDs: CVE-2020-15779, GHSA-9h4g-27m8-qjrg
Record: https://patchnext.com/advisories/cve-2020-15779 (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: High (CVSS 7.5)
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 socket.io-file: affected <= 2.0.31

## Suggested inspection (read-only)
- `npm ls socket.io-file --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 socket.io-file.
- 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-9h4g-27m8-qjrg (OSV record GHSA-9h4g-27m8-qjrg lists affected ranges: npm socket.io-file >=0 <=2.0.31)
- Verified: https://github.com/advisories/GHSA-9h4g-27m8-qjrg (GitHub-reviewed advisory GHSA-9h4g-27m8-qjrg lists affected ranges: npm socket.io-file >=0 <=2.0.31)

Commands are suggestions: review each one before running it.