CVE-2026-75612

yt-mcp attachments could upload arbitrary readable server files

velesnitski · yt-mcp

First documented disclosure · Review checkpoint

Summary

A controlled attachment path could combine local secret reading with external upload.

Severity and exploitation evidence

High · 7.5/10 · CVSS 3.1. Severity source.

Exploitation not established: Malicious exploitation remains unverified in the reviewed originals. A demonstration or absence from KEV does not establish exploitation status.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

add_attachment checked file existence without directory confinement before uploading to YouTrack.

Conditions required

A malicious MCP caller or an agent steered through prompt injection, plus access to the destination YouTrack issue.

Potential impact

Any readable process file can be uploaded. A related snapshot-name traversal can write JSON outside the intended directory.

Affected versions and configurations

yt-mcp: < 1.18.1.

Fix and mitigation status

1.18.1.

Practical next steps

Apply the issue-specific correction: 1.18.1. Restrict the affected tool or endpoint until the correction is deployed.

Operating lesson

Treat local-file attachment tools as both a read boundary and an export boundary.

Evidence and limits

Earliest reviewed public evidence 2026-07-09; CVE publication 2026-11-18. CVSS 3.1 7.5 is attributed to GitHub_M in the CNA record.

Sources