dbcve.org
Octopus ServerApplication · Octopus

CVE-2025-0525

HIGH · 7.5 CVSS v3.1 Published 2025-02-11
Fix available
A fix is available. Upgrade to 2024.3.13007 / 2024.4.6995 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 Server the preview import feature could be leveraged to identify the existence of a target file. This could provide an adversary with information that may aid in further attacks against the server.

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 versions of Octopus Server, the preview import feature allows an attacker to determine whether a target file exists on the server by manipulating import requests. This file existence disclosure is an information leak that could reveal system paths, configuration files, or other sensitive file locations useful for planning further attacks.

MitigationImplement strict input validation and access controls on the preview import feature to prevent unauthorized file path probing. Consider restricting the feature to authenticated users with appropriate permissions and validating that requested file paths fall within allowed directories.

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:>= 2020.6.4592, < 2024.3.13007>= 2024.4.401, < 2024.4.6995

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Check installed Octopus Server version
    Locate the Octopus Server installation and identify its version number, typically found in the application UI under 'About' or in the installation directory's version info
    Affected if The installed version falls within the affected ranges: >= 2020.6.4592 AND < 2024.3.13007, OR >= 2024.4.401 AND < 2024.4.6995
  2. Identify if preview import feature is accessible
    Determine whether the preview import functionality is exposed in the Octopus Server deployment. This may involve reviewing enabled features, extensions, or API endpoints related to import operations
    Affected if The preview import feature is enabled or accessible in the deployment
  3. Verify authentication controls on import endpoints
    Review the access control configuration for import-related API endpoints to confirm whether authentication is required for preview import requests
    Affected if The preview import endpoints are accessible without authentication or to unauthenticated/unauthorized users
  4. Check for unauthenticated or low-privilege access
    Inspect whether the preview import feature permits requests from users without proper authorization or from anonymous/guest accounts
    Affected if Unauthenticated users or users with limited permissions can trigger the preview import functionality

A user is affected if their Octopus Server version is within the affected ranges AND the preview import feature is accessible to unauthorized or unauthenticated users.

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.13007 / 2024.4.6995 or later
Fixed in 2024.3.130072024.4.6995
Interim mitigation

Implement strict input validation and access controls on the preview import feature to prevent unauthorized file path probing. Consider restricting the feature to authenticated users with appropriate permissions and validating that requested file paths fall within allowed directories.

Recommended fix High confidence

2024.4.6995 or later (or 2024.3.13007 or later for the 2024.3.x branch)

  1. 1. Identify your current Octopus Server version using the Octopus Admin portal or command line
  2. 2. If running version 2020.6.4592 through 2024.3.x, plan upgrade to version 2024.3.13007 or later
  3. 3. If running version 2024.4.401 through 2024.4.x, plan upgrade to version 2024.4.6995 or later
  4. 4. Review Octopus Server release notes for your target version for any migration requirements
  5. 5. Back up your Octopus Server database before upgrading
  6. 6. Perform the upgrade following standard Octopus Server upgrade procedures
  7. 7. Verify the server starts successfully and the web portal is accessible

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

Fix this in Octopus Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0525 — 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-0525 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