Quick answers
- Is CVE-2026-77364 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-77364 being exploited in the wild.
- How severe is CVE-2026-77364?
- Medium severity, with a CVSS score of 6.5, published 12 October 2026.
- Which products and versions are affected?
- obsidian-tc (npm) < 1.3.1, SEMVER:introduced=0,fixed=1.3.1; The-40-Thieves Obsidian-Tc before 1.3.1.
- Is there a fix for CVE-2026-77364?
- Yes. obsidian-tc (npm): upgrade to 1.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-77364 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-77364?
- Check whether you run obsidian-tc (npm) or The-40-Thieves Obsidian-Tc at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- obsidian-tc (npm): upgrade to 1.3.1 or later
npm install obsidian-tc@1.3.1
Technical details
The vulnerability stems from undefined readPaths and writePaths ACL settings defaulting to allow-all, combined with strictReadDefault being ignored on direct file requests (only enforced during enumeration). Control directories (.obsidian, .git, .trash) were excluded from enumeration only, not from direct reads. An authenticated caller can invoke direct read operations like read_note('.obsidian/plugins/*/data.json') to retrieve sensitive data. Version 1.3.1 fixes this by enforcing hard default-deny for control directories regardless of allowlist configuration and applying strictReadDefault uniformly to both direct requests and enumeration.
Affected products
- The-40-Thieves obsidian-tc before 1.3.1
Identifiers
- CVE-2026-77364
- GHSA-cvp8-vvgf-69q4
Timeline
- 2026-10-12: disclosed
- 2026-07-01: patched