CVE-2025-58334
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 IDE Services before 2025.5.0.1086, 2025.4.2.2164 users without appropriate permissions could assign high-privileged role for themselves
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 · high confidenceIn JetBrains IDE Services before versions 2025.5.0.1086 and 2025.4.2.2164, an authorization bypass exists where users lacking appropriate permissions can assign high-privileged roles to themselves. This is a privilege escalation vulnerability in the role assignment functionality.
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< 2025.4.2.2164>= 2025.5, < 2025.5.0.1086CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 the installed JetBrains IDE Services versionCheck the product version through the IDE Services administration console, or query the service metadata using the vendor-provided version endpoint (typically /api/v1/system/info or similar). Compare the version string to the affected ranges: < 2025.4.2.2164 or >= 2025.5.0.0 and < 2025.5.0.1086.Affected if The installed version falls within the affected ranges listed in the CVE.
-
Verify the role assignment feature is accessibleConfirm that the IDE Services instance has user management and role assignment functionality enabled. This is typically accessible through the administration panel under User Management or Access Control settings.Affected if User and role management features are active in the environment.
-
Review user role assignment audit logsExamine IDE Services audit logs or access logs for role assignment operations. Look for API calls or actions that modify user roles, particularly assignments to high-privileged roles (administrator, superuser, or equivalent). Check for any role changes initiated by users who should not have elevated permissions.Affected if Role assignment actions exist in logs where the requesting user lacked prior administrative privileges.
-
Inspect current user role mappingsExport or list all user-to-role mappings from the IDE Services user directory. Identify accounts that hold high-privileged roles and verify whether the assigned roles match the expected authorization scope for those users.Affected if Any user account holds a high-privileged role that was not explicitly assigned through an authorized administrative process.
You are affected if your IDE Services version is before 2025.4.2.2164 or between 2025.5.0.0 and 2025.5.0.1085, and users with limited permissions could have assigned themselves elevated roles through the role assignment interface.
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 · scoped2025.4.2.21642025.5.0.1086
Apply the vendor patches (2025.5.0.1086 or 2025.4.2.2164 or later) to fix the missing authorization checks in the role assignment mechanism. Audit existing user role assignments for any unauthorized privilege escalation.
2025.4.2.2164 (for 2025.4.x branch) or 2025.5.0.1086 (for 2025.5.x branch)
- Identify the currently installed JetBrains IDE Services version
- Upgrade to version 2025.4.2.2164 or later if using the 2025.4.x branch
- If using the 2025.5.x branch, upgrade to version 2025.5.0.1086 or later
- Verify the upgrade was successful by checking the IDE Services version
- Test that the authorization controls now properly prevent unprivileged users from assigning high-privileged roles
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58334 — 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-2025-58334 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