CVE-2026-77363

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

GHSA-pqh8-4pj7-32xx ↗EUVD-2026-97733 ↗

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-346 Origin Validation Error
ETK-2026-1400Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:npm/obsidian-tc
8d 09h 49msince last run
25mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h13m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

obsidian-tc before 1.3.1 exposes its Streamable HTTP transport without Host, Origin, or DNS-rebinding validation. A malicious web page may access the local MCP endpoint and obtain vault access when the service uses the documented loopback configuration with authentication disabled.

mitigation

Upgrade obsidian-tc to version 1.3.1 or later. Until upgraded, do not run the loopback HTTP transport with authentication disabled and restrict access to the local endpoint.

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.16%4th percentile
agent run time
25m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-12 17:45Z
Δ 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:45Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1400",
  "cve_id": "CVE-2026-77363",
  "display_id": "CVE-2026-77363",
  "ghsa_id": "GHSA-pqh8-4pj7-32xx",
  "euvd_id": "EUVD-2026-97733",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cross-origin local vault access in obsidian-tc HTTP transport",
  "summary": "obsidian-tc before 1.3.1 exposes its Streamable HTTP transport without Host, Origin, or DNS-rebinding validation. A malicious web page may access the local MCP endpoint and obtain vault access when the service uses the documented loopback configuration with authentication disabled.",
  "mitigation": "Upgrade obsidian-tc to version 1.3.1 or later. Until upgraded, do not run the loopback HTTP transport with authentication disabled and restrict access to the local endpoint.",
  "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": [
    346
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
  "epss_score": 0.0016,
  "epss_percentile": 0.0448,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 24.8699643,
  "t0_at": "2026-10-12T17:45:57.107000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-12T17:45:57.107000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T17:45:57.107000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-77363"
    }
  }
}

published 2026-10-12 18:33Z
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.