GitHub Advisory Database15 days ago

obsidian-tc tokens can access arbitrary configured vaults

Impact Tool dispatch did not check the caller-supplied input.vault against the caller's bound vault (ctx.vaultId); the folder ACL was a single global instance and the JWT carried no vault claim. As a result, any valid token could read, write, or delete any configured vault by pas

Published October 23, 2026 · 5:29 PM
Impact Tool dispatch did not check the caller-supplied input.vault against the caller's bound vault (ctx.vaultId); the folder ACL was a single global instance and the JWT carried no vault claim. As a result, any valid token could read, write, or delete any configured vault by pas
Read

Source: GitHub Advisory Database

Ask AI about this articleBeta

The AI only has access to this article — it won't make up facts. Try:

AI can be wrong. Cross-check before sharing.

Supporting evidence0 items
Community check0 comments
No votes yet
0% real0% fake