Vulnerability feed

CVE and vendor PSIRT advisories from 13 sources, last 30 days. Updated hourly, last run Oct 26 05:05 UTC

Critical in the last 24 hours

1602 in 30 days

Newly known exploited

In the last 24 hours, CISA KEV and vendor reports

Sources checked

Every hour, see the list

New in the last 24 hours

161-73% vs 7-day avg of 598

2 critical, 47 high, 62 medium, 30 low

Expand	Severity	Score	Advisory	Title	Source	Published
	High	7.1	CVE-2026-115478	obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults The-40-Thieves, obsidian-tcThe-40-Thieves obsidian-tc, obsidian-tc	NVD	Oct 23 15:17 UTC
CVE-2026-115478obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults Executive summary obsidian-tc, a Model Context Protocol server for Obsidian note vaults, has a flaw in versions 1.0.1 through 1.31.4 that can cause memory notes to overwrite other notes and leave data inconsistent after failed operations. An authorized caller with the required memory-tool permissions could unintentionally destroy the contents of a vault note outside the entity being written. The advisory states the issue is fixed in version 1.31.4, and that is the recommended action. Technical summary The flaw is a path collision and ownership validation problem in memory note materialization, combined with write ordering errors. Tools such as create_entity, link_entities, rename_entity, unlink_entities and delete_entity write memory notes at computed memory/<type>/<name>.md paths without reliably checking ownership, so a hand-authored note or orphan whose name sanitizes to the same path can have its body overwritten; rename_entity also overwrites a foreign note at its destination path. SQLite rows and relations are changed before filesystem work that can fail, leaving the graph inconsistent with disk. Exploitation requires an authorized caller with the relevant memory-tool permissions, and delete_entity still needs its deletion permission and destructive confirmation. Affected versions are 1.0.1 through 1.31.4 and the fixed version is 1.31.4. The advisory does not state a CVSS score or any workaround beyond noting that restore_note snapshots mitigate overwrites only where snapshots are enabled and the note was previously written by obsidian-tc. Detection guidance is not stated. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Impact if exploited ConfidentialityNone IntegrityHigh AvailabilityLow How it is exploited Attack vector Network Attack complexity Low Attack requirements None Privileges required Low User interaction None CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X Affects The-40-Thieves obsidian-tc The-40-Thieves obsidian-tc obsidian-tc NIST National Vulnerability DatabasePublished Oct 23, 2026 15:17 UTC Read the advisory
	High	7.1	CVE-2026-115477	obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults The-40-Thieves, obsidian-tcThe-40-Thieves obsidian-tc, obsidian-tc	NVD	Oct 23 15:17 UTC
CVE-2026-115477obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults Executive summary obsidian-tc, a server that lets AI agents work with Obsidian note vaults, has a flaw that could let a client carry out destructive vault operations without a human approving them. The advisory says the flaw affected versions 1.13.0 through 1.31.4 in certain Streamable HTTP deployments, and it is fixed in version 1.31.4. Technical summary The flaw is an approval bypass in the confirmation flow for dispatch-gated tool calls, where the server accepted a call-bound requestState as proof of human approval even though it was issued before the elicitation/create step was asked. It affects versions from 1.13.0 until 1.31.4 on Streamable HTTP deployments with auth.jwtSecret configured and a client declaring elicitation.form support. A client acting incorrectly or under an attacker's control could complete tools marked destructive: true or requiring a scope with a human-in-the-loop floor, while still needing the caller's ordinary tool permissions. The advisory states the fix is in version 1.31.4 and notes the fix cannot stop a malicious client from reporting a fabricated approval. No workaround is stated, and no detection guidance or information on exploitation in the wild is stated. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Impact if exploited ConfidentialityNone IntegrityHigh AvailabilityLow How it is exploited Attack vector Network Attack complexity Low Attack requirements None Privileges required Low User interaction None CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X Affects The-40-Thieves obsidian-tc The-40-Thieves obsidian-tc obsidian-tc NIST National Vulnerability DatabasePublished Oct 23, 2026 15:17 UTC Read the advisory
	Medium	4.3	CVE-2026-77362	obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults The-40-ThievesThe-40-Thieves obsidian-tc	NVD	Oct 13 14:17 UTC
CVE-2026-77362obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults From the advisory obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults. Prior to 1.3.1, bridge tools do not consistently apply the read access-control list (ACL) to every returned field. The tasks_filter tool exposes group counts derived from denied notes, makemd_query passes unfiltered sibling result fields through, and list_templates exposes template paths and parsed user-function bodies without a read-whitelist check. An authenticated caller can consequently infer or read data from notes outside the caller's read ACL. Version 1.3.1 fixes the vulnerability by filtering path-attributable fields and applying the read whitelist to list_templates. Impact if exploited ConfidentialityLow IntegrityNone AvailabilityNone How it is exploited Attack vector Network Attack complexity Low Privileges required Low User interaction None Scope Unchanged CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Affects The-40-Thieves The-40-Thieves obsidian-tc NIST National Vulnerability DatabasePublished Oct 13, 2026 14:17 UTC Read the advisory
	Medium	4.7	CVE-2026-77361	obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults The-40-ThievesThe-40-Thieves obsidian-tc	NVD	Oct 13 14:17 UTC
CVE-2026-77361obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults From the advisory obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults. Prior to 1.3.1, read access-control list (ACL) checks use a lexical vault-relative path while containment checks use the resolved path. An in-vault symlink under an allowed glob that resolves into a denied folder can therefore bypass the read ACL and expose files in the denied folder. Exploitation requires an out-of-band-planted symlink and does not permit an escape from the vault root. Version 1.3.1 fixes the vulnerability by applying ACL checks to the resolved vault-relative path. Impact if exploited ConfidentialityHigh IntegrityNone AvailabilityNone How it is exploited Attack vector Local Attack complexity High Privileges required Low User interaction None Scope Unchanged CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N Affects The-40-Thieves The-40-Thieves obsidian-tc NIST National Vulnerability DatabasePublished Oct 13, 2026 14:17 UTC Read the advisory
	Critical	9.9	CVE-2026-77366	obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults The-40-ThievesThe-40-Thieves obsidian-tc	NVD	Oct 12 18:17 UTC
CVE-2026-77366obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults From the advisory obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults. Prior to 1.3.1, tool dispatch does not compare the caller-controlled input.vault value with the vault bound to the caller, the JSON Web Token (JWT) has no vault claim, and the folder access-control list is shared globally. Any valid token can therefore select another configured vault and read, write, or delete its contents through affected tools. Version 1.3.1 fixes the vulnerability by binding tokens and request context to a vault and rejecting mismatched input.vault values before scope checks. Impact if exploited ConfidentialityHigh IntegrityHigh AvailabilityHigh How it is exploited Attack vector Network Attack complexity Low Privileges required Low User interaction None Scope Changed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H Affects The-40-Thieves The-40-Thieves obsidian-tc NIST National Vulnerability DatabasePublished Oct 12, 2026 18:17 UTC Read the advisory
	Medium	6.5	CVE-2026-77364	obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults The-40-ThievesThe-40-Thieves obsidian-tc	NVD	Oct 12 18:17 UTC
CVE-2026-77364obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults From the advisory obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults. Prior to 1.3.1, undefined readPaths and writePaths settings allow all paths, strictReadDefault does not protect direct requests, and the .obsidian, .git, and .trash control directories are excluded only during enumeration. An authenticated caller can directly read sensitive files such as .obsidian/plugins/*/data.json, potentially exposing plugin API keys, Obsidian Sync passwords, and other in-vault data. Version 1.3.1 fixes the vulnerability by denying the control directories by default and enforcing strictReadDefault on direct request paths. Impact if exploited ConfidentialityHigh IntegrityNone AvailabilityNone How it is exploited Attack vector Network Attack complexity Low Privileges required Low User interaction None Scope Unchanged CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Affects The-40-Thieves The-40-Thieves obsidian-tc NIST National Vulnerability DatabasePublished Oct 12, 2026 18:17 UTC Read the advisory
	High	8.8	CVE-2026-77363	obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults The-40-ThievesThe-40-Thieves obsidian-tc	NVD	Oct 12 18:17 UTC
CVE-2026-77363obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults From the advisory obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults. Prior to 1.3.1, the Streamable HTTP transport does not validate the Host or Origin header or enable DNS-rebinding protection. When the documented loopback configuration uses auth.mode set to none, a malicious web page can send requests to the local MCP endpoint and receive unrestricted vault access through the http-local caller. Version 1.3.1 fixes the vulnerability by enabling host, origin, and DNS-rebinding validation. Impact if exploited ConfidentialityHigh IntegrityHigh AvailabilityHigh How it is exploited Attack vector Network Attack complexity Low Privileges required None User interaction Required Scope Unchanged CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Affects The-40-Thieves The-40-Thieves obsidian-tc NIST National Vulnerability DatabasePublished Oct 12, 2026 18:17 UTC Read the advisory

Example	Finds
	Every word appears somewhere: title, summaries, IDs, vendor, or product
	An exact phrase
	One vendor. product: for a product, vp: for either
	Commas mean any of them, in every field
	Severity: critical, high, medium, low, or unknown
	CVSS score, with >, >=, <, or <=
	A score range
	Known exploited. is:kev works too, and kev:no leaves them out
	One source, by name
	Confidentiality impact: high, low, none, or any (low or high)
	Integrity and availability work the same way
	An advisory or CVE ID, or part of one
	A minus sign leaves out whatever the term matches

Vulnerability feed

Executive summary

Technical summary

Impact if exploited

How it is exploited

Affects

Executive summary

Technical summary

Impact if exploited

How it is exploited

Affects

From the advisory

Impact if exploited

How it is exploited

Affects

From the advisory

Impact if exploited

How it is exploited

Affects

From the advisory

Impact if exploited

How it is exploited

Affects

From the advisory

Impact if exploited

How it is exploited

Affects

From the advisory

Impact if exploited

How it is exploited

Affects

Search syntax

Welcome to CVEsee.org

What is CVEsee.org?

Disclaimer

You are leaving CVEsee.org

Install CVEsee