Octopus
Products
10- 81 CVEs
- 64 CVEs
- 19 CVEs
- 5 CVEs
- 2 CVEs
- 2 CVEs
- 1 CVE
- Halibut1 CVEnuget
- 1 CVE
- 1 CVE
Recent CVEs
129| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2024-9194 | Cri | 0.64 | 9.8 | 0.00 | Sep 30, 2024 | Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Linux and Microsoft Windows Octopus Server on Windows, Linux allows SQL Injection.This issue affects Octopus Server: from 2024.1.0 before 2024.1.13038, from 2024.2.0 before… | ||
| CVE-2022-2572 | Cri | 0.64 | 9.8 | 0.01 | Nov 1, 2022 | In affected versions of Octopus Server where access is managed by an external authentication provider, it was possible that the API key/keys of a disabled/deleted user were still valid after the access was revoked. | ||
| CVE-2022-2778 | Cri | 0.64 | 9.8 | 0.01 | Sep 30, 2022 | In affected versions of Octopus Deploy it is possible to bypass rate limiting on login using null bytes. | ||
| CVE-2021-31819 | Cri | 0.64 | 9.8 | 0.02 | Sep 22, 2021 | In Halibut versions prior to 4.4.7 there is a deserialisation vulnerability that could allow remote code execution on systems that already trust each other based on certificate verification. | ||
| CVE-2018-11320 | Cri | 0.64 | 9.8 | 0.01 | May 21, 2018 | In Octopus Deploy 2018.4.4 through 2018.5.1, Octopus variables that are sourced from the target do not have sensitive values obfuscated in the deployment logs. | ||
| CVE-2018-18850 | Hig | 0.61 | 8.8 | 0.12 | Oct 31, 2018 | In Octopus Deploy 2018.8.0 through 2018.9.x before 2018.9.1, an authenticated user with permission to modify deployment processes could upload a maliciously crafted YAML configuration, potentially allowing for remote execution of arbitrary code, running in the same context as… | ||
| CVE-2026-0704 | Cri | 0.59 | 9.1 | 0.00 | Feb 25, 2026 | 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. | ||
| CVE-2022-2782 | Cri | 0.59 | 9.1 | 0.01 | Oct 27, 2022 | In affected versions of Octopus Server it is possible for a session token to be valid indefinitely due to improper validation of the session token parameters. | ||
| CVE-2026-124628 | Hig | 0.57 | — | 0.00 | Nov 12, 2026 | In affected versions of Octopus Server, incorrect validation of changes a user made to their own LDAP identity allowed them to edit that identity even when an Administrator had disabled self-service identity editing. This could result in the user gaining membership of teams… | ||
| CVE-2026-124627 | Hig | 0.57 | — | 0.00 | Nov 12, 2026 | In affected versions of Octopus Server, incorrect validation of the external identity linked to a newly registered user could result in that user receiving the LDAP-mapped team memberships and associated permissions of another user. This issue only affects instances with LDAP… | ||
| CVE-2026-116835 | Hig | 0.57 | — | 0.00 | Nov 12, 2026 | In affected versions of Octopus Server, insufficient validation of custom claims on OIDC accounts allowed a user with permission to edit accounts to cause Octopus Server to issue signed OIDC tokens that impersonate a different project. This could grant access to external… | ||
| CVE-2026-96414 | Hig | 0.57 | — | 0.00 | Nov 11, 2026 | In affected versions of Octopus Server, insufficient integrity protection of authentication cookies, combined with incorrect validation of permissions assigned to a user that allowed them to view users or audit events, could result in the user escalating their privileges to… | ||
| CVE-2026-116870 | Hig | 0.57 | — | 0.00 | Oct 27, 2026 | In affected versions of Octopus Server, OIDC token issuer validation was performed inconsistently. This could result in a token issued from a suitably configured non legitimate issuer being accepted as a token belonging to a service account from a legitimate trusted issuer.… | ||
| CVE-2026-102488 | Hig | 0.57 | — | 0.00 | Oct 8, 2026 | In affected versions, Octopus Server incorrectly evaluates multiple scoped permission assignments, allowing a highly privileged user to obtain deployment permissions beyond those actually granted to them. | ||
| CVE-2026-102478 | Hig | 0.57 | — | 0.00 | Oct 7, 2026 | In affected versions of Octopus Server, an authenticated user with permission to modify roles could bypass the protections preventing access abuse resulting in privilege escalation. It was possible for the built-in role to be weakened and the attacker's account added to a… | ||
| CVE-2026-101169 | Hig | 0.57 | — | 0.00 | Sep 29, 2026 | In affected versions of Octopus Server, an authenticated user with permissions to edit an Environment or Project can set specifically crafted JSON content for the object. Insecure deserialization of this content allows the user to execute arbitrary code in the Octopus Server… | ||
| CVE-2026-92355 | Hig | 0.57 | — | 0.01 | Sep 16, 2026 | In affected versions of Octopus Server, a user with permission to modify non built-in external feeds could exploit a path traversal flaw to overwrite arbitrary files on the server, which in some configurations could lead to remote code execution. | ||
| CVE-2026-12878 | Hig | 0.57 | 8.8 | 0.00 | Aug 25, 2026 | In affected versions of the Codefresh platform an authenticated user can utilize an API endpoint to elevate to Admin permissions. | ||
| CVE-2025-0539 | Hig | 0.57 | 8.8 | 0.00 | Apr 10, 2025 | In affected Microsoft Windows versions of Octopus Deploy, the server can be coerced into sending server-side requests that contain authentication material allowing a suitably positioned attacker to compromise the account running Octopus Server and potentially the host… | ||
| CVE-2024-2975 | Hig | 0.57 | 8.8 | 0.00 | Apr 9, 2024 | A race condition was identified through which privilege escalation was possible in certain configurations. |
- risk 0.64cvss 9.8epss 0.00
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Linux and Microsoft Windows Octopus Server on Windows, Linux allows SQL Injection.This issue affects Octopus Server: from 2024.1.0 before 2024.1.13038, from 2024.2.0 before…
- risk 0.64cvss 9.8epss 0.01
In affected versions of Octopus Server where access is managed by an external authentication provider, it was possible that the API key/keys of a disabled/deleted user were still valid after the access was revoked.
- risk 0.64cvss 9.8epss 0.01
In affected versions of Octopus Deploy it is possible to bypass rate limiting on login using null bytes.
- risk 0.64cvss 9.8epss 0.02
In Halibut versions prior to 4.4.7 there is a deserialisation vulnerability that could allow remote code execution on systems that already trust each other based on certificate verification.
- risk 0.64cvss 9.8epss 0.01
In Octopus Deploy 2018.4.4 through 2018.5.1, Octopus variables that are sourced from the target do not have sensitive values obfuscated in the deployment logs.
- risk 0.61cvss 8.8epss 0.12
In Octopus Deploy 2018.8.0 through 2018.9.x before 2018.9.1, an authenticated user with permission to modify deployment processes could upload a maliciously crafted YAML configuration, potentially allowing for remote execution of arbitrary code, running in the same context as…
- risk 0.59cvss 9.1epss 0.00
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.
- risk 0.59cvss 9.1epss 0.01
In affected versions of Octopus Server it is possible for a session token to be valid indefinitely due to improper validation of the session token parameters.
- risk 0.57cvss —epss 0.00
In affected versions of Octopus Server, incorrect validation of changes a user made to their own LDAP identity allowed them to edit that identity even when an Administrator had disabled self-service identity editing. This could result in the user gaining membership of teams…
- risk 0.57cvss —epss 0.00
In affected versions of Octopus Server, incorrect validation of the external identity linked to a newly registered user could result in that user receiving the LDAP-mapped team memberships and associated permissions of another user. This issue only affects instances with LDAP…
- risk 0.57cvss —epss 0.00
In affected versions of Octopus Server, insufficient validation of custom claims on OIDC accounts allowed a user with permission to edit accounts to cause Octopus Server to issue signed OIDC tokens that impersonate a different project. This could grant access to external…
- risk 0.57cvss —epss 0.00
In affected versions of Octopus Server, insufficient integrity protection of authentication cookies, combined with incorrect validation of permissions assigned to a user that allowed them to view users or audit events, could result in the user escalating their privileges to…
- risk 0.57cvss —epss 0.00
In affected versions of Octopus Server, OIDC token issuer validation was performed inconsistently. This could result in a token issued from a suitably configured non legitimate issuer being accepted as a token belonging to a service account from a legitimate trusted issuer.…
- risk 0.57cvss —epss 0.00
In affected versions, Octopus Server incorrectly evaluates multiple scoped permission assignments, allowing a highly privileged user to obtain deployment permissions beyond those actually granted to them.
- risk 0.57cvss —epss 0.00
In affected versions of Octopus Server, an authenticated user with permission to modify roles could bypass the protections preventing access abuse resulting in privilege escalation. It was possible for the built-in role to be weakened and the attacker's account added to a…
- risk 0.57cvss —epss 0.00
In affected versions of Octopus Server, an authenticated user with permissions to edit an Environment or Project can set specifically crafted JSON content for the object. Insecure deserialization of this content allows the user to execute arbitrary code in the Octopus Server…
- risk 0.57cvss —epss 0.01
In affected versions of Octopus Server, a user with permission to modify non built-in external feeds could exploit a path traversal flaw to overwrite arbitrary files on the server, which in some configurations could lead to remote code execution.
- risk 0.57cvss 8.8epss 0.00
In affected versions of the Codefresh platform an authenticated user can utilize an API endpoint to elevate to Admin permissions.
- risk 0.57cvss 8.8epss 0.00
In affected Microsoft Windows versions of Octopus Deploy, the server can be coerced into sending server-side requests that contain authentication material allowing a suitably positioned attacker to compromise the account running Octopus Server and potentially the host…
- risk 0.57cvss 8.8epss 0.00
A race condition was identified through which privilege escalation was possible in certain configurations.