# CVE-2025-0589: Information disclosure in Octopus Server

> Unauthenticated attackers can retrieve Active Directory user and group details via API endpoints when AD authentication is enabled.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2025
- **Updated:** 11 Feb 2025
- **Also known as:** GHSA-p76j-345f-qxpw

## What is CVE-2025-0589?

CVE-2025-0589 is a medium-severity vulnerability in Octopus Octopus Server, published on 11 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In affected versions of Octopus Deploy where customers are using Active Directory for authentication it was possible for an unauthenticated user to make an API request against two endpoints which would retrieve some data from the associated Active Directory. The requests when crafted correctly would return specific information from user profiles (Email address/UPN and Display name) from one endpoint and group information ( Group ID and Display name) from the other. This vulnerability does not expose data within the Octopus Server product itself.

Weakness: CWE-648 (Incorrect Use of Privileged APIs)

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

It affects 1 product.


Products: Octopus Octopus Server.

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

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

## Is CVE-2025-0589 being exploited?

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

## Other vulnerabilities in Octopus Octopus Server

- [CVE-2022-2572](https://insights.sbomify.com/CVE-2022-2572/): Auth bypass in Octopus Server (critical 9.8)
- [CVE-2022-2778](https://insights.sbomify.com/CVE-2022-2778/): Security feature bypass in Octopus Server (critical 9.8)
- [CVE-2018-11320](https://insights.sbomify.com/CVE-2018-11320/): Information disclosure in n/a (critical 9.8)
- [CVE-2022-2782](https://insights.sbomify.com/CVE-2022-2782/): Auth bypass in Octopus Server (critical 9.1)
- [CVE-2024-2975](https://insights.sbomify.com/CVE-2024-2975/): Race condition in Octopus Server (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0589 is a medium-severity vulnerability in Octopus Octopus Server, published on 11 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0589 in the wild and no public exploit code.

Affected product: Octopus Octopus Server. 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-0589/ (Markdown: https://insights.sbomify.com/CVE-2025-0589/index.md)
```

## Sources

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

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