CVE-2026-49370
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.1.13162 information disclosure was possible on fetchApp requests
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 confidenceJetBrains YouTrack before version 2026.1.13162 contains an information disclosure vulnerability in the fetchApp API endpoint. The vulnerability allows unauthenticated or improperly authorized attackers to potentially access sensitive information through fetchApp requests, resulting in HIGH severity due to the potential exposure of configuration data, user information, or system details.
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.1.13162CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 if JetBrains YouTrack is installedCheck for YouTrack installation by looking for the YouTrack service or process: on Windows check Services panel for 'YouTrack' service, on Linux check for /opt/youtrack or /home/youtrack directories, or look for java processes running YouTrackAffected if YouTrack is not installed - the vulnerability does not apply
-
Check the installed YouTrack versionLog into YouTrack as an administrator, go to Administration > System > Overview to view the exact version number, or check the version file in the YouTrack installation directory (VERSION.txt or similar)Affected if The installed version is lower than 2026.1.13162 - the environment is affected
-
Verify the fetchApp endpoint accessibilityCheck if the web interface is exposed by attempting to access the fetchApp endpoint (typically /app/fetchApp or similar REST endpoint) from an unauthenticated perspective - note that this is a passive check onlyAffected if The endpoint is reachable without authentication and the version is in the affected range - exploitation is possible
The environment is affected if JetBrains YouTrack is installed and the running version is below 2026.1.13162, making the fetchApp endpoint vulnerable to unauthenticated information disclosure.
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.1.13162
Upgrade JetBrains YouTrack to version 2026.1.13162 or later to remediate this vulnerability. If immediate patching is not possible, restrict network access to the YouTrack server and review API endpoint access controls as a temporary mitigation.
2026.1.13162
- Upgrade YouTrack to version 2026.1.13162 or later to address the information disclosure vulnerability in fetchApp requests
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49370 — 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-49370 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