CVE
yt-mcp arbitrary file read in MCP add_attachment tool
- Exploited
- No known exploitation
- Fix
- Fixed in 1.18.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.18.1.
Summary
The yt-mcp YouTrack MCP server has a path traversal flaw in its add_attachment tool that lets an attacker read any file the server process can access and upload its contents to a YouTrack issue. The attack can be carried out remotely over the network, without logging in and without any user action.
Original description
yt-mcp is a YouTrack MCP server for Claude Code. Prior to 1.18.1, add_attachment in src/yt_mcp/tools/attachments.py accepts a caller-controlled file_path, checks only that the file exists, reads it without directory confinement, and uploads the bytes to a YouTrack issue. A compromised MCP client or an LLM steered by indirect prompt injection can read any file accessible to the server process and exfiltrate secrets through an issue the caller can access. The same release also permits get_project_health to interpolate a caller-controlled project value into snapshot filenames, allowing parent-directory traversal to write JSON files outside the snapshots directory. This issue is fixed in version 1.18.1.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.18.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-75612 (yt-mcp: Path traversal in the add_attachment MCP tool allows arbitrary local file read and exfiltration), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-75612 (entry last updated 2026-11-18):
Affected:
- velesnitski yt-mcp: fixed in 1.18.1
Fixed versions: 1.18.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-75612 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-75612 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/velesnitski/yt-mcp/security/advisories/GHSA-99mq-fjjc-6v9j
- https://github.com/velesnitski/yt-mcp/commit/b70054b180e6ec7a03f70ee4744518d96d2fba8a
- https://github.com/velesnitski/yt-mcp/releases/tag/v1.18.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-75612
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-75612"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- velesnitski yt-mcp
fixed in 1.18.1
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · velesnitski/yt-mcp · Advisory GHSA-99mq-fjjc-6v9j |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-75612 |
| Record | NVD · CVE-2026-75612 |
| Other links 2 | |
| Repository | GitHub · velesnitski/yt-mcp · Commit b70054b1 |
| Repository | GitHub · velesnitski/yt-mcp · Release v1.18.1 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-75612
Is CVE-2026-75612 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-75612?
yt-mcp: before 1.18.1.Source: cve.now feed data
How do I fix CVE-2026-75612?
Upgrade to a fixed version: 1.18.1.Source: cve.now feed data