Vulnerability feed

CVE and vendor PSIRT advisories from 13 sources, last 30 days. Updated hourly, last run Oct 26 04: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

154-74% vs 7-day avg of 597

2 critical, 44 high, 61 medium, 27 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

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

Search syntax

Welcome to CVEsee.org

What is CVEsee.org?

Disclaimer

You are leaving CVEsee.org

Install CVEsee