dbcve.org
Octopus ServerApplication · Octopus

CVE-2025-0526

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-11
Fix available
A fix is available. Upgrade to 2024.3.13097 / 2024.4.7091 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
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.

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 · moderate confidence

In affected Octopus Deploy versions, an API endpoint allows file uploads to unexpected locations on the host due to insufficient validation on an upload field. This path traversal-like issue could allow attackers to write files outside intended directories, potentially bypassing security controls.

MitigationImplement strict path validation and sanitization on file upload API endpoints to ensure files can only be written to permitted directories. Restrict upload paths and verify all file path inputs before processing.

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
Octopus ServerApplication
Affected:>= 2022.4.791, < 2024.3.13097>= 2024.4.401, < 2024.4.7091

CVSS 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
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate Octopus Server installation directory
    On Windows, check the default path C:\Program Files\Octopus Deploy\Octopus\ or look for the Octopus.Server.exe file. On Linux, check /opt/octopus or the configured installation directory. Run 'octopus.server --version' if the CLI is available.
    Affected if Cannot locate the installation to verify version
  2. Determine installed Octopus Server version
    Check the About page in the Octopus Web UI, or run 'octopus.server version' from the installation directory, or inspect the OctopusServer.exe file properties for version info.
    Affected if Version falls within >= 2022.4.791, < 2024.3.13097 OR >= 2024.4.401, < 2024.4.7091
  3. Confirm API access is enabled
    Check if the Octopus API is accessible by attempting to reach the base URL (e.g., https://your-octopus-server/api) from an authorized network location. Verify that the Server administration has not disabled or restricted API access.
    Affected if API endpoint is exposed and accessible to untrusted users or networks
  4. Audit file system for unexpected files outside upload directories
    Review the Octopus data directory (typically the Artifacts, Packages, or Logs folders) and surrounding directories for files with unexpected extensions, scripts, or executables that were not uploaded through known, legitimate processes. Compare file creation timestamps against known deployment activities.
    Affected if Files exist outside designated upload directories or contain suspicious content not matching expected upload patterns

You are affected if your Octopus Server version is within the affected ranges AND the API endpoint is accessible to potential attackers, or if unexpected files are found outside intended upload directories.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2024.3.13097 / 2024.4.7091 or later
Fixed in 2024.3.130972024.4.7091
Interim mitigation

Implement strict path validation and sanitization on file upload API endpoints to ensure files can only be written to permitted directories. Restrict upload paths and verify all file path inputs before processing.

Recommended fix High confidence

2024.3.13097 or later (2024.3.x LTS) OR 2024.4.7091 or later (2024.4.x)

  1. 1. Identify your current Octopus Server version in the UI (Configuration > About) or via the API
  2. 2. If your version is >= 2022.4.791 and < 2024.3.13097, plan upgrade to 2024.3.13097 or later in the 2024.3.x LTS line
  3. 3. If your version is >= 2024.4.401 and < 2024.4.7091, plan upgrade to 2024.4.7091 or later in the 2024.4.x line
  4. 4. Review Octopus Deploy release notes for your target version for any breaking changes
  5. 5. Perform a full backup of your Octopus database and configuration before upgrading
  6. 6. Follow standard Octopus Server upgrade procedure (stop service, run installer/upgrade, verify startup)
  7. 7. After upgrade, verify that file upload API endpoints enforce proper authorization and path validation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Octopus Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0526 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0526 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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