# CVE-2025-0539: Server-side request forgery in Octopus Server

> An attacker can force Octopus Server to send authenticated requests, potentially compromising the server account and underlying infrastructure.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Apr 2025
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-5h88-xc4r-2q76

## What is CVE-2025-0539?

CVE-2025-0539 is a medium-severity server-side request forgery vulnerability in Octopus Octopus Server, published on 10 Apr 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

In affected Microsoft Windows versions of Octopus Deploy, the server can be coerced into sending server-side requests that contain authentication material allowing a suitably positioned attacker to compromise the account running Octopus Server and potentially the host infrastructure itself.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Octopus Octopus Server.

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

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

## Is CVE-2025-0539 being exploited?

There is no known exploitation of CVE-2025-0539 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-0539 and fix it if it is affected.

What it is: CVE-2025-0539 is a medium-severity server-side request forgery vulnerability in Octopus Octopus Server, published on 10 Apr 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-0539 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-0539/ (Markdown: https://insights.sbomify.com/CVE-2025-0539/index.md)
```

## Sources

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

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