NVD / CVE Program· CNA Octopus

CVE-2026-0704: In affected version of Octopus Deploy it was possible to remove files and/or contents of files on the host using an API endpoint.

Noroxi assessment

Priority: Monitor (action score 23/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.37% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. Special conditions such as timing or configuration are required.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In 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.

MediumCVSS 5.9 · v4.0—No exploit No fix recorded

Path traversal

Published: Feb 25, 2026
Updated: Jun 17, 2026
EPSS: 0.3% · 31th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 23 / 40 · 5.9 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · Octopus: 5.9; NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
octopus	octopus server	cpe:2.3:a:octopus:octopus_server
linux	linux kernel	cpe:2.3:o:linux:linux_kernel
microsoft	windows	cpe:2.3:o:microsoft:windows

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

octopus octopus server2023.1.4189 and later · before 2025.3.14715

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Octopus). Independent of NVD's CPE analysis and usually ahead of it.

Octopus Deploy Octopus Server
- 2023.0.0 and later · before 2025.3.14715affected
- 2025.4.0 and later · before 2025.4.10359affected

Same product

octopus: all records

Other highest-scoring records for the same primary product.

CVE-2018-18850In Octopus Deploy 2018.8.0 through 2018.9.x before 2018.9.1, an authenticated user with permission to modify deployment processes could uplo
40Plan
CVE-2022-2572In affected versions of Octopus Server where access is managed by an external authentication provider, it was possible that the API key/keys
39Monitor
CVE-2022-2778In affected versions of Octopus Deploy it is possible to bypass rate limiting on login using null bytes.
39Monitor

Published before and after this one in the same product

← EarlierCVE-2025-0588Feb 11, 2025 · In affected versions of Octopus Server it was possible for a user with sufficient access to set custom headers in all server responses.
23Monitor
← EarlierCVE-2025-0539Apr 10, 2025 · In affected Microsoft Windows versions of Octopus Deploy, the server can be coerced into sending server-side requests that contain authentic
23Monitor
Later →CVE-2026-3236Mar 5, 2026 · In affected versions of Octopus Server it was possible to create a new API key from an existing access token resulting in the new API key ha
9Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

oub3ll4finder

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

OctopusBugcrowd · paid · up to $6,000

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
Administrator privileges are required.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality
Integrity
Availability

Attack vector: Network
Attack complexity: High
Privileges required: High
User interaction: None
Scope: X

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

advisories.octopus.com/post/2026/sa2026-01

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records