CVE-2026-49385
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.13570 improper access control allowed low-privileged users to modify service accounts
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 improper access control vulnerability in JetBrains YouTrack where low-privileged users can modify service accounts due to insufficient authorization checks. Service accounts typically have elevated system privileges, so unauthorized modification could lead to privilege escalation or service disruption.
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.13570CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 YouTrack versionAccess YouTrack Administration > System > Overview or check the build number in the footer of any YouTrack page. The version format appears as year.build-number (e.g., 2026.1.xxxxx).Affected if The installed version number is less than 2026.1.13570 (e.g., 2026.1.10000 or earlier).
-
Confirm service accounts existNavigate to Administration > Users > Service Accounts (or similar service account management interface in your YouTrack instance). Check if any service accounts are configured or created.Affected if One or more service accounts are present in the system.
-
Test service account modification access for low-privileged usersLog in with a non-administrator user account (e.g., a standard user with minimal permissions). Attempt to navigate to the service account management area or modify an existing service account configuration.Affected if A low-privileged user (non-admin) can access or modify service accounts without receiving an authorization/permission error.
-
Review user role assignments for service account permissionsIn Administration > Users > Roles (or Permissions), examine the permissions assigned to non-admin user groups. Look for permissions related to service account create/read/update/delete actions.Affected if Non-administrator roles or groups have permissions to create, modify, or delete service accounts.
You are affected if your YouTrack version is below 2026.1.13570 AND service accounts exist AND low-privileged users can modify those service accounts without proper authorization controls.
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.13570
Upgrade YouTrack to version 2026.1.13570 or later to receive the access control fix.
2026.1.13570
- Create a full backup of the YouTrack database and configuration files before proceeding
- Stop the YouTrack service to prevent data inconsistency during upgrade
- Download YouTrack version 2026.1.13570 or later from the official JetBrains website or your existing license portal
- Follow the standard YouTrack upgrade procedure for your deployment method (ZIP bundle, Docker, or JAR)
- Start the YouTrack service and verify the application loads correctly
- Log in as an administrator and confirm the upgrade was successful by checking the YouTrack version in Administration > Application section
- Verify that the authorization fix is working by testing that low-privileged users can no longer modify service accounts
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49385 — 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-49385 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