CVE-2026-0704
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 · uneditedIn affected version of Octopus Deploy it was possible to remove files and/or contents of files 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 confidenceOctopus Deploy contains a path traversal vulnerability in an API endpoint that allows removal of arbitrary files on the host filesystem due to insufficient validation of a user-supplied field. The lack of input sanitization enables attackers to manipulate file paths outside the expected workflow boundaries.
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>= 2023.1.4189, < 2025.3.14715CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Octopus Server installationLocate the Octopus Server installation directory, typically at C:\Program Files\Octopus or /opt/octopus on Linux, or check for the Octopus.Manager.exe process running as a service.Affected if Octopus Server software is present on the system
-
Determine installed Octopus Server versionOpen the Octopus Web UI and navigate to the Configuration > About page, or run 'octo version' from the command line if the Octopus CLI is installed, or check the Windows service properties.Affected if The exact version number can be retrieved from the installation
-
Compare version against affected rangeCheck if the installed version is >= 2023.1.4189 AND < 2025.3.14715. Only versions within this range are vulnerable.Affected if Version falls within >= 2023.1.4189 and < 2025.3.14715 indicates the vulnerable code is present
The environment is affected if Octopus Server is installed with a version matching the range >= 2023.1.4189 and < 2025.3.14715.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2025.3.14715
Implement strict input validation and path canonicalization on affected API endpoints, using allowlist validation and path traversal checks to ensure file operations remain within intended directories.
2025.3.14715 or later
- Backup the Octopus Server database before upgrading
- Review the release notes for version 2025.3.14715 for any specific upgrade requirements or known issues
- Schedule a maintenance window for the upgrade process
- Upgrade Octopus Server to version 2025.3.14715 or later
- Verify the upgrade was successful and test that the API endpoint now properly validates file paths
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2026-0704 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0704 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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