CVE-2026-54618

CRITICAL CVSS 9.4 PoC Available
Published: 2026-09-17
Modified: 2026-09-17
Enriched via mock
Tenable Plugin

Checking the public Tenable catalog…

AI Threat Summary

CVE-2026-54618 is a critical vulnerability with a CVSS score of 9.4 affecting the target software. Authentication can be bypassed allowing unauthenticated access. Threat hunters should monitor for exploit attempts and apply vendor patches immediately.

Description

Obsidian Web MCP is a secure remote MCP server for Obsidian vaults. Prior to 0.2.0, /oauth/authorize issues an authorization code without a login, consent, or session check, and /oauth/token can exchange that code for the static VAULT_MCP_TOKEN without authenticating a client. An unauthenticated remote caller who can reach the intended tunnel deployment can therefore call /mcp and use vault_read, vault_write, vault_search, vault_list, vault_move, and vault_delete against the entire vault. Optional PKCE does not prevent an attacker-initiated flow, and unauthenticated /oauth/register also exposes a client_credentials path by returning the configured VAULT_OAUTH_CLIENT_SECRET. This issue is fixed in version 0.2.0.

Attack Chain
1
Reconnaissance

Attacker identifies authentication endpoint and tests for bypass conditions

2
Initial Access

Attacker exploits CVE-2026-54618 authentication flaw to gain unauthorized access without valid credentials

3
Discovery

Attacker enumerates accessible resources, users, and configurations

4
Collection

Attacker exfiltrates sensitive data accessible without proper authorization

MITRE ATT&CK Techniques
T1078 Valid Accounts
Initial Access

Authentication bypass grants attacker access as legitimate user

T1548 Abuse Elevation Control Mechanism
Privilege Escalation

Bypassed auth may grant elevated or admin-level permissions

Indicators of Compromise
Type Value Description
user_agent Mozilla/5.0 (compatible; exploit/1.0) Generic exploit scanner user agent pattern
url /api/vuln-endpoint?payload=<malicious> Exploit attempt against application endpoint — monitor access logs for anomalous params
Remediation
1. Apply vendor-supplied security patches immediately. 2. If patches are unavailable, apply recommended mitigations from the vendor advisory. 3. Enable WAF rules or IDS signatures to detect exploitation attempts. 4. Monitor logs for indicators of compromise listed above. 5. Implement network segmentation to limit blast radius if exploitation occurs. 6. Subscribe to vendor security advisories for this product.