Skip to content

← Actionable
Medium, CVSS 5.1amended

coursevault-preview has a path traversal due to improper base-directory boundary validation

CVE-2026-35613GHSA-9h9m-rr67-9jpg

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (coursevault-preview 0.1.1), 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.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.1 · CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2026-35613: 0.14% estimated exploitation activity in the next 30 days; percentile 3.44 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary coursevault-preview versions prior to 0.1.1 contain a path traversal vulnerability in the resolveSafe utility. The boundary check used String.prototype.startsWith(baseDir) on a normalized path, which does not enforce a directory boundary. An attacker who controls the relativePath argument to affected CoursevaultPreview methods may be able to read files outside the configured baseDir when a sibling directory exists whose name shares the same string prefix. Details The vulnerable code in src/utils/errors.ts: Because the check is a raw string prefix test rather than a path-boundary test, the following bypass is possible: Any file whose absolute path begins with the baseDir string — including files in sibling directories that share a name prefix — passes the guard and can be accessed by the caller through affected file-access methods. The fix replaces the check with a separator-aware comparison: Impact An application that passes untrusted input as the relativePath argument to…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-9h9m-rr67-9jpg

  2. Revision 1 · created ·

    Published from osv record GHSA-9h9m-rr67-9jpg

Agent brief

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

# Patch Next advisory brief: CVE-2026-35613

Advisory: coursevault-preview has a path traversal due to improper base-directory boundary validation
IDs: CVE-2026-35613, GHSA-9h9m-rr67-9jpg
Record: https://patchnext.com/advisories/cve-2026-35613 (revision 2, source checked 26 Oct 2026, 12:47 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: coursevault-preview 0.1.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm coursevault-preview: affected < 0.1.1; fixed in 0.1.1

## Suggested inspection (read-only)
- `npm ls coursevault-preview --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 coursevault-preview.
- 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-9h9m-rr67-9jpg (OSV record GHSA-9h9m-rr67-9jpg lists affected ranges: npm coursevault-preview >=0 <0.1.1 (fixed))
- Verified: https://github.com/advisories/GHSA-9h9m-rr67-9jpg (GitHub-reviewed advisory GHSA-9h9m-rr67-9jpg lists affected ranges: npm coursevault-preview >=0 <0.1.1)

Commands are suggestions: review each one before running it.

Loading voting…