CVE-2026-57922
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn JetBrains YouTrack before 2026.2.16593 project settings disclosure via the MCP was possible
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is an information disclosure vulnerability in JetBrains YouTrack where project settings could be exposed through the MCP (Model Context Protocol) integration. The vulnerability affects versions prior to 2026.2.16593, allowing unauthorized access to sensitive project configuration data via the MCP interface.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2026.2.16593CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed YouTrack versionAccess YouTrack admin area and navigate to Administration > Overview, or check the build number displayed on the login page. Compare this version number to the affected range: any version prior to 2026.2.16593 is vulnerable.Affected if The installed YouTrack version is less than 2026.2.16593.
-
Determine if MCP integration is enabledNavigate to Administration > Plugins or Integration settings in YouTrack. Look for MCP (Model Context Protocol) integration settings. Check whether any MCP connectors are configured or enabled.Affected if MCP integration is enabled and configured in YouTrack.
-
Verify MCP access controlsReview the user permissions and roles assigned to MCP-connected external services. Check if MCP connections have been granted access to project-level settings without proper restrictions.Affected if MCP integration has access to project configuration data without adequate access controls.
-
Inspect MCP endpoint accessibilityIf you have administrative access, review the MCP API endpoints and check whether project settings are exposed through the MCP interface by examining the available MCP commands or capabilities.Affected if Project settings are accessible through MCP endpoints without authentication or authorization barriers.
You are affected if your YouTrack version is below 2026.2.16593 AND the MCP integration is enabled, allowing potential exposure of project configuration data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2026.2.16593
Update YouTrack to version 2026.2.16593 or later to patch the vulnerability. If the MCP integration is not required, consider disabling it as an additional hardening measure.
2026.2.16593
- Upgrade JetBrains YouTrack to version 2026.2.16593 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57922 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-57922 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data