Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.8amended

obsidian-local-rest-api: Authenticated path traversal via URL-encoded %2F in /vault/{path} — arbitrary host file read/write/delete

GHSA-62gx-5q78-wrvx

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (obsidian-local-rest-api 4.1.3), 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

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary The Local REST API's `/vault/{path}` endpoints (GET/PUT/PATCH/POST/DELETE) percent-decode the request path *inside the handler — after* Express has already routed and normalized it, then hand it to the Obsidian vault adapter with no confinement check. A literal `../` is resolved/rejected at the routing layer (→ 404), but `%2F` is not a separator there, so `..%2F..%2F` survives routing and is only turned into a real `/` by the handler's `decodeURIComponent`, reconstituting a `../` traversal that walks out of the vault. An authenticated client can read, write, or delete arbitrary files on the host with the Obsidian process's privileges.

Details Framework: Express (`import express from "express"`; routes registered via `this.api.route("/vault/*")…`). The vulnerable line — in `src/requestHandler.ts`, every vault handler (`vaultGet`, `vaultPut`, `vaultPatch`, `vaultPost`, `vaultDelete`) derives the path like this: ```ts const rawPath = decodeURIComponent(…

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

    Amended from osv record GHSA-62gx-5q78-wrvx

  2. Revision 2 · amended ·

    Amended from ghsa record GHSA-62gx-5q78-wrvx

  3. Revision 1 · created ·

    Published from osv record GHSA-62gx-5q78-wrvx

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-62gx-5q78-wrvx

Advisory: obsidian-local-rest-api: Authenticated path traversal via URL-encoded %2F in /vault/{path} — arbitrary host file read/write/delete
IDs: GHSA-62gx-5q78-wrvx
Record: https://patchnext.com/advisories/ghsa-62gx-5q78-wrvx (revision 3, source checked 3 Nov 2026, 06:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: obsidian-local-rest-api 4.1.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm obsidian-local-rest-api: affected < 4.1.3; fixed in 4.1.3

## Suggested inspection (read-only)
- `npm ls obsidian-local-rest-api --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 obsidian-local-rest-api.
- 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-62gx-5q78-wrvx (OSV record GHSA-62gx-5q78-wrvx lists affected ranges: npm obsidian-local-rest-api >=0)
- Verified: https://github.com/advisories/GHSA-62gx-5q78-wrvx (GitHub-reviewed advisory GHSA-62gx-5q78-wrvx lists affected ranges: npm obsidian-local-rest-api >=0 <4.1.3)
- Verified: https://osv.dev/vulnerability/GHSA-62gx-5q78-wrvx (OSV record GHSA-62gx-5q78-wrvx lists affected ranges: npm obsidian-local-rest-api >=0 <4.1.3 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…