CVE-2026-77366

waiting for further signalsZero needs more public information before it can validate it.

GHSA-84c9-qqpq-2pq5 ↗EUVD-2026-97737 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
The-40-Thieves obsidian-tc < 1.3.1
fixed in 1.3.1
CWE-639 Authorization Bypass Through User-Controlled Key
ETK-2026-1397Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:npm/obsidian-tc
8d 10h 01msince last run
30mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h50m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

obsidian-tc versions before 1.3.1 do not properly bind authenticated requests to the caller’s assigned vault. An attacker with any valid token may access content in other configured vaults, including reading, changing, or deleting it, when those vaults are available to the server.

mitigation

Upgrade obsidian-tc to version 1.3.1 or later. Restrict access to valid tokens and limit exposure of configured vaults until the upgrade is complete.

fixed in 1.3.1

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.31%22nd percentile
agent run time
30m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-12 17:54Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-12 17:54Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-77366

{
  "etk_id": "ETK-2026-1397",
  "cve_id": "CVE-2026-77366",
  "display_id": "CVE-2026-77366",
  "ghsa_id": "GHSA-84c9-qqpq-2pq5",
  "euvd_id": "EUVD-2026-97737",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cross-vault authorization bypass in obsidian-tc",
  "summary": "obsidian-tc versions before 1.3.1 do not properly bind authenticated requests to the caller’s assigned vault. An attacker with any valid token may access content in other configured vaults, including reading, changing, or deleting it, when those vaults are available to the server.",
  "mitigation": "Upgrade obsidian-tc to version 1.3.1 or later. Restrict access to valid tokens and limit exposure of configured vaults until the upgrade is complete.",
  "vendor": "The-40-Thieves",
  "product": "obsidian-tc",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 1.3.1"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "1.3.1"
      ],
      "package_name": "obsidian-tc",
      "purl": "pkg:npm/obsidian-tc"
    }
  ],
  "cwes": [
    639
  ],
  "cvss_score": 9.9,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": 0.0031,
  "epss_percentile": 0.2223,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 30.046169466666665,
  "t0_at": "2026-10-12T17:54:31.642000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-12T17:54:31.642000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T17:54:31.642000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-77366"
    }
  }
}

published 2026-10-12 18:14Z
last change 2026-10-21 04:45Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.