Path traversal in oak allows transfer of hidden files within the served root directory

Exploitation

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

CVSS 4.0

7.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P · score source

EPSS

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

Summary By default oak does not allow transferring of hidden files with Context.send API. However, this can be bypassed by encoding / as its URL encoded form %2F. Details 1.) Oak uses decodeComponent which seems to be unexpected. This is also the reason why it is not possible to access a file that contains URL encoded characters unless the client URL encodes it first. 2.) The function isHidden is flawed since it only checks if the first subpath is hidden, allowing secrets to be read from subdir/.env. PoC In terminal: Impact For an attacker this has potential to read sensitive user data or to gain access to server secrets.

Published by the source

1 Nov 2024, 21:37 UTC

Last modified by the source

1 Nov 2024, 22:27 UTC

Source last checked

26 Oct 2026, 12:31 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-qm92-93fv-vh7m

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-qm92-93fv-vh7m

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

# Patch Next advisory brief: CVE-2024-49770

Advisory: Path traversal in oak allows transfer of hidden files within the served root directory
IDs: CVE-2024-49770, GHSA-qm92-93fv-vh7m
Record: https://patchnext.com/advisories/cve-2024-49770 (revision 3, source checked 26 Oct 2026, 12:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
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 @oakserver/oak: affected <= 14.1.0

## Suggested inspection (read-only)
- `npm ls @oakserver/oak --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 @oakserver/oak.
- 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-qm92-93fv-vh7m (OSV record GHSA-qm92-93fv-vh7m lists affected ranges: npm @oakserver/oak >=0 <=14.1.0)
- Verified: https://github.com/advisories/GHSA-qm92-93fv-vh7m (GitHub-reviewed advisory GHSA-qm92-93fv-vh7m lists affected ranges: npm @oakserver/oak >=0 <=14.1.0)

Commands are suggestions: review each one before running it.