{"items":[{"id":"NVI-00010109","kind":"vulnerability","title":"obsidian-tc tokens can access arbitrary configured vaults","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-84c9-qqpq-2pq5","CVE-2026-77366"],"plain_summary":"GitHub lists this reviewed advisory for obsidian-tc. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-d92778082657b3a527a0d599bc00647a"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 1.3.1 for obsidian-tc. Confirm the publisher’s latest guidance.","source_ids":["sr-d4992bd25a2947004901ecaf8e3d5233"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-23T17:29:18.000Z","value":"9.9 critical","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-14c62c41f99fe4e0bf48bfc7af1e3d08"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.309%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.23716. Missing scores are unknown.","source_id":"sr-d92778082657b3a527a0d599bc00647a"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-14c62c41f99fe4e0bf48bfc7af1e3d08","url":"https://github.com/advisories/GHSA-84c9-qqpq-2pq5","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-84c9-qqpq-2pq5","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:07:08.657Z"},{"id":"sr-d4992bd25a2947004901ecaf8e3d5233","url":"https://github.com/advisories/GHSA-84c9-qqpq-2pq5","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-84c9-qqpq-2pq5","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-05T11:39:18.274Z"},{"id":"sr-d92778082657b3a527a0d599bc00647a","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-77366","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:20:46.866Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-14c62c41f99fe4e0bf48bfc7af1e3d08"],"technology":"obsidian-tc","known_exclusions":[],"conditions_summary":"### Impact\nTool 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 passing `input.vault`, defeating multi-tenant isolation across ~90 tool sites. (`resources/read` was the only surface that already guarded this.)\n\n### Patches\nFixed in **1.3.1** (the fix was developed on the `v1.3.0` tag, which never published to npm; 1.3.1 is the first published release with the fix). Upgrade to `>= 1.3.1`.\n\n### Workarounds\nRun a single vault per server process, or isolate each tenant on a separate process/credential.\n\n### Fix\nA central `input.vault === ctx.vaultId` guard was added in dispatch before the scope check.","public_affected_ranges":["< 1.3.1"]},{"certainty":"source_listed","source_ids":["sr-d4992bd25a2947004901ecaf8e3d5233"],"technology":"obsidian-tc","known_exclusions":[],"conditions_summary":"### Impact\nTool 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 passing `input.vault`, defeating multi-tenant isolation across ~90 tool sites. (`resources/read` was the only surface that already guarded this.)\n\n### Patches\nFixed in **1.3.1** (the fix was developed on the `v1.3.0` tag, which never published to npm; 1.3.1 is the first published release with the fix). Upgrade to `>= 1.3.1`.\n\n### Workarounds\nRun a single vault per server process, or isolate each tenant on a separate process/credential.\n\n### Fix\nA central `input.vault === ctx.vaultId` guard was added in dispatch before the scope check.","public_affected_ranges":["SEMVER: introduced 0; fixed 1.3.1"]}],"null_published_at":"2026-11-08T08:10:32.020Z","source_updated_at":"2026-10-23T17:29:18.000Z","source_disclosed_at":"2026-10-23T17:29:17.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T22:07:08.657Z"},{"id":"NVI-00010109","kind":"vulnerability","title":"obsidian-tc tokens can access arbitrary configured vaults","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-84c9-qqpq-2pq5","CVE-2026-77366"],"plain_summary":"GitHub lists this reviewed advisory for obsidian-tc. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-14c62c41f99fe4e0bf48bfc7af1e3d08"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 1.3.1 for obsidian-tc. Confirm the publisher’s latest guidance.","source_ids":["sr-d4992bd25a2947004901ecaf8e3d5233"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-23T17:29:18.000Z","value":"9.9 critical","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-14c62c41f99fe4e0bf48bfc7af1e3d08"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-14c62c41f99fe4e0bf48bfc7af1e3d08","url":"https://github.com/advisories/GHSA-84c9-qqpq-2pq5","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-84c9-qqpq-2pq5","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:07:08.657Z"},{"id":"sr-d4992bd25a2947004901ecaf8e3d5233","url":"https://github.com/advisories/GHSA-84c9-qqpq-2pq5","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-84c9-qqpq-2pq5","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-05T11:39:18.274Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-14c62c41f99fe4e0bf48bfc7af1e3d08"],"technology":"obsidian-tc","known_exclusions":[],"conditions_summary":"### Impact\nTool 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 passing `input.vault`, defeating multi-tenant isolation across ~90 tool sites. (`resources/read` was the only surface that already guarded this.)\n\n### Patches\nFixed in **1.3.1** (the fix was developed on the `v1.3.0` tag, which never published to npm; 1.3.1 is the first published release with the fix). Upgrade to `>= 1.3.1`.\n\n### Workarounds\nRun a single vault per server process, or isolate each tenant on a separate process/credential.\n\n### Fix\nA central `input.vault === ctx.vaultId` guard was added in dispatch before the scope check.","public_affected_ranges":["< 1.3.1"]},{"certainty":"source_listed","source_ids":["sr-d4992bd25a2947004901ecaf8e3d5233"],"technology":"obsidian-tc","known_exclusions":[],"conditions_summary":"### Impact\nTool 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 passing `input.vault`, defeating multi-tenant isolation across ~90 tool sites. (`resources/read` was the only surface that already guarded this.)\n\n### Patches\nFixed in **1.3.1** (the fix was developed on the `v1.3.0` tag, which never published to npm; 1.3.1 is the first published release with the fix). Upgrade to `>= 1.3.1`.\n\n### Workarounds\nRun a single vault per server process, or isolate each tenant on a separate process/credential.\n\n### Fix\nA central `input.vault === ctx.vaultId` guard was added in dispatch before the scope check.","public_affected_ranges":["SEMVER: introduced 0; fixed 1.3.1"]}],"null_published_at":"2026-11-07T00:57:04.328Z","source_updated_at":"2026-10-23T17:29:18.000Z","source_disclosed_at":"2026-10-23T17:29:17.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T22:07:08.657Z"},{"id":"NVI-00010109","kind":"vulnerability","title":"obsidian-tc tokens can access arbitrary configured vaults","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-84c9-qqpq-2pq5","CVE-2026-77366"],"plain_summary":"GitHub lists this reviewed advisory for obsidian-tc. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-14c62c41f99fe4e0bf48bfc7af1e3d08"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-23T17:29:18.000Z","value":"9.9 critical","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-14c62c41f99fe4e0bf48bfc7af1e3d08"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-14c62c41f99fe4e0bf48bfc7af1e3d08","url":"https://github.com/advisories/GHSA-84c9-qqpq-2pq5","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-84c9-qqpq-2pq5","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:07:08.657Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-14c62c41f99fe4e0bf48bfc7af1e3d08"],"technology":"obsidian-tc","known_exclusions":[],"conditions_summary":"### Impact\nTool 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 passing `input.vault`, defeating multi-tenant isolation across ~90 tool sites. (`resources/read` was the only surface that already guarded this.)\n\n### Patches\nFixed in **1.3.1** (the fix was developed on the `v1.3.0` tag, which never published to npm; 1.3.1 is the first published release with the fix). Upgrade to `>= 1.3.1`.\n\n### Workarounds\nRun a single vault per server process, or isolate each tenant on a separate process/credential.\n\n### Fix\nA central `input.vault === ctx.vaultId` guard was added in dispatch before the scope check.","public_affected_ranges":["< 1.3.1"]}],"null_published_at":"2026-10-31T22:13:48.415Z","source_updated_at":"2026-10-23T17:29:18.000Z","source_disclosed_at":"2026-10-23T17:29:17.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T22:07:08.657Z"}],"next_cursor":null,"snapshot_revision":"42594"}