# CVE-2025-58334: Privilege escalation in IDE Services

> Unauthorized users can assign themselves high-privileged roles in JetBrains IDE Services, requiring an upgrade to the latest version.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-3xq3-4xq8-mfmx

## What is CVE-2025-58334?

CVE-2025-58334 is a high-severity vulnerability in JetBrains IDE Services, published on 28 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In JetBrains IDE Services before 2025.5.0.1086, 
2025.4.2.2164 users without appropriate permissions could assign high-privileged role for themselves

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-58334?

It affects 1 product.


Products: Jetbrains Ide Services.

## How do I fix CVE-2025-58334?

No fix has been published for CVE-2025-58334 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-58334 being exploited?

There is no known exploitation of CVE-2025-58334 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-58334 and fix it if it is affected.

What it is: CVE-2025-58334 is a high-severity vulnerability in JetBrains IDE Services, published on 28 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-58334 in the wild and no public exploit code.

Affected product: JetBrains IDE Services. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-58334/ (Markdown: https://insights.sbomify.com/CVE-2025-58334/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-58334
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-58334
- OSV: https://osv.dev/vulnerability/CVE-2025-58334

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-58334/
Summaries are generated and may contain mistakes; the official description above is the record.