Quick answers
- Is CVE-2026-77361 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-77361 being exploited in the wild.
- How severe is CVE-2026-77361?
- Medium severity, with a CVSS score of 4.7, published 13 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-77361?
- 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-77361 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-77361?
- 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 is a path canonicalization bypass in ACL enforcement: read ACL checks evaluated the lexical (as-provided) request path against the allowlist, while containment checks resolved symlinks to their true paths and discarded the result. An in-vault symlink under an allowed glob pattern that resolved to a denied folder would pass the ACL check but reach restricted files. The fix applies ACL checks to the resolved vault-relative path rather than the lexical path, and requires no new filesystem calls beyond what containment checking already performed.
Affected products
- The-40-Thieves obsidian-tc before 1.3.1
Identifiers
- CVE-2026-77361
- GHSA-c5xx-h28h-f682
Timeline
- 2026-10-13: disclosed
- 2026-07-01: patched