OS
Product
Octopus Server
66
CVEs
0
On KEV
9.8
Max CVSS
0
New 30D
Severity mix
Critical 6High 19Medium 37Low 4
Watch
Add Octopus Server to your stack to get only the CVEs that touch what you run.
| CVE | CVSS | Published | Summary · affected versions |
|---|---|---|---|
| CVE-2026-4881 | 6.5 | Jun 4 | In affected versions of Octopus Server, permissions were not checked correctly resulting in any authenticated user being able to make server level changes using a certain API… Affected: 2023.1.4189 before 2025.4.10545; 2026.1.675 before 2026.1.11313 |
| CVE-2024-6972 | 6.5 | Jul 25 | In affected versions of Octopus Server under certain circumstances it is possible for sensitive variables to be printed in the task log in clear-text Affected: 2024.1.437 before 2024.1.12759; 2024.2.101 before 2024.2.9193 |
| CVE-2022-2828 | 6.5 | Oct 13 | In affected versions of Octopus Server it is possible to reveal information about teams via the API due to an Insecure Direct Object Reference (IDOR) vulnerability Affected: 2022.1.2121 through 2022.1.3135; 2022.2.0 through 2022.2.7897; 2022.3.0 through 2022.3.10586 |
| CVE-2022-2528 | 6.5 | Sep 9 | In affected versions of Octopus Deploy it is possible to upload a package to built-in feed with insufficient permissions after re-indexing packages Affected: 3.0.0 through 4.1.10; 2018.1.0 through 2021.3.13021; 2022.1.0 before 2022.1.3106; 2022.2.6729 before 2022.2.7718; 2022.3.348 before 2022.3.7782 |
| CVE-2019-8944 | 6.5 | Feb 20 | An Information Exposure issue in the Terraform deployment step in Octopus Deploy before 2019.1.8 (and before 2018.10.4 LTS) allows remote authenticated users to view sensitive… Affected: 2018.11.0 before 2019.1.8 |
| CVE-2022-3614 | 6.1 | Jan 3 | In affected versions of Octopus Deploy users of certain browsers using AD to sign-in to Octopus Server were able to bypass authentication checks and be redirected to the… Affected: 3.5 before 2022.3.10750; 2022.4 before 2022.4.8063 |
| CVE-2022-29890 | 6.1 | Jul 15 | In affected versions of Octopus Server the help sidebar can be customized to include a Cross-Site Scripting payload in the support link Affected: 2019.7.0 before 2021.3.13021; 2022.1.2121 before 2022.1.2849; 2022.3.348 before 2022.3.2387; 2022.2.6729 |
| CVE-2022-23184 | 6.1 | Feb 7 | In affected Octopus Server versions when the server HTTP and HTTPS bindings are configured to localhost, Octopus Server will allow open redirects Affected: 2021.2.0 before 2021.2.8011; 2021.3.0 before 2021.3.11057 |
| CVE-2017-11348 | 5.7 | Jul 17 | In Octopus Deploy 3.x before 3.15.4, an authenticated user with PackagePush permission to upload packages could upload a maliciously crafted NuGet package, potentially overwriting… Affected: 3.0.0; 3.0.1; 3.0.2; 3.0.3; 3.0.4; 3.0.5; +34 more |
| CVE-2022-4008 | 5.5 | May 10 | In affected versions of Octopus Deploy it is possible to upload a zipbomb file as a task which results in Denial of Service Affected: 0.9 before 2022.3.11043; 2022.4.791 before 2022.4.8401 |
| CVE-2025-0513 | 5.4 | Feb 11 | In affected versions of Octopus Server error messages were handled unsafely on the error page Affected: 2024.3.164 before 2024.3.12985; 2024.4.401 before 2024.4.6962 |
| CVE-2025-0526 | 5.4 | Feb 11 | In affected versions of Octopus Deploy it was possible to upload files to unexpected locations on the host using an API endpoint Affected: 2022.4.791 before 2024.3.13097; 2024.4.401 before 2024.4.7091 |
| CVE-2024-4456 | 5.4 | May 8 | In affected versions of Octopus Server with certain access levels it was possible to embed a Cross-Site Scripting payload on the audit page Affected: 3.0.0 before 2023.4.8338; 2024.1.437 before 2024.1.11127 |
| CVE-2022-4898 | 5.4 | Jan 31 | In affected versions of Octopus Server the help sidebar can be customized to include a Cross-Site Scripting payload in the support link Affected: 2019.7.0 before 2022.2.8552; 2022.3.348 before 2022.3.10750; 2022.4.791 before 2022.4.8319 |
| CVE-2025-0589 | 5.3 | Feb 11 | In affected versions of Octopus Deploy where customers are using Active Directory for authentication it was possible for an unauthenticated user to make an API request against two… Affected: 2020.3.3 before 2024.3.13071; 2024.4.401 before 2024.4.7065 |
| CVE-2022-4870 | 5.3 | May 18 | In affected versions of Octopus Deploy it is possible to discover network details via error message Affected: 3.0.0 before 2023.1.9879; 2023.2.2028 before 2023.2.8159 |
| CVE-2022-2507 | 5.3 | Apr 19 | In affected versions of Octopus Deploy it is possible to render user supplied input into the webpage Affected: before 2023.1.9794; 2022.4.0 before 2022.4.8332; 2023.1.0 before 2023.1.6715 |
| CVE-2022-2508 | 5.3 | Oct 27 | In affected versions of Octopus Server it is possible to reveal the existence of resources in a space that the user does not have access to due to verbose error messaging Affected: before 2022.1.3264; 2022.2.0 before 2022.2.8351; 2022.3.0 before 2022.3.10586; 2022.4.0 before 2022.4.2898 |
| CVE-2022-2720 | 5.3 | Oct 12 | In affected versions of Octopus Server it was identified that when a sensitive value is a substring of another value, sensitive value masking will only partially work Affected: 3.16.4 before 2022.1.3154; 2022.2.6729 before 2022.2.7934; 2022.3.348 before 2022.3.10586 |
| CVE-2022-2783 | 5.3 | Oct 6 | In affected versions of Octopus Server it was identified that a session cookie could be used as the CSRF token Affected: 3.12.0 before 2022.1.3154; 2022.2.6729 before 2022.2.7897; 2022.3.348 before 2022.3.10586 |
| CVE-2022-2781 | 5.3 | Oct 6 | In affected versions of Octopus Server it was identified that the same encryption process was used for both encrypting session cookies and variables Affected: 3.2.10 before 2022.1.3154; 2022.2.6729 before 2022.2.7897; 2022.3.348 before 2022.3.10586 |
| CVE-2022-1901 | 5.3 | Aug 19 | In affected versions of Octopus Deploy it is possible to unmask sensitive variables by using variable preview Affected: 2019.1.0 through 2019.7.3; 2020.1.0 through 2020.6.5449; 2021.1.6959 through 2021.3.13021; 2022.1.0 before 2022.1.3009; 2022.2.6729 before 2022.2.7244; 2022.3.348 before 2022.3.4953 |
| CVE-2022-30532 | 5.3 | Jul 19 | In affected versions of Octopus Deploy, there is no logging of changes to artifacts within Octopus Deploy Affected: 0.9 before 2021.3.13021; 2022.1.0 before 2022.1.2849; 2022.3.348 before 2022.3.2387 |
| CVE-2022-1881 | 5.3 | Jul 15 | In affected versions of Octopus Server an Insecure Direct Object Reference vulnerability exists where it is possible for a user to download Project Exports from a Project they do… Affected: 2021.1.6959 before 2021.3.13021; 2022.1.2121 before 2022.1.2894; 2022.2.6729 before 2022.2.6971; 2022.3.348 before 2022.3.2616 |
| CVE-2026-12702 | 4.9 | Jul 24 | In affected versions of Octopus Deploy Insufficient checks on the project trigger actions allows an unauthorized user to trigger a deployment Affected: 2023.1.4189 before 2026.1.11587; 2026.2.61 before 2026.2.13190 |
| CVE-2025-0588 | 4.9 | Feb 11 | In affected versions of Octopus Server it was possible for a user with sufficient access to set custom headers in all server responses Affected: 2020.1.0 before 2024.3.13097; 2024.4.401 before 2024.4.7091 |
| CVE-2019-14525 | 4.9 | Aug 5 | In Octopus Deploy 2019.4.0 through 2019.6.x before 2019.6.6, and 2019.7.x before 2019.7.6, an authenticated system administrator is able to view sensitive values by visiting a… Affected: 2019.7.0 before 2019.7.6 |
| CVE-2026-3237 | 4.3 | Mar 17 | In affected versions of Octopus Server it was possible for a low privileged user to manipulate an API request to change the signing key expiration and revocation time frames via… Affected: before 2025.3.14731; 2025.4.51 before 2025.4.10359; 2026.1.675 before 2026.1.5571 |
| CVE-2026-3236 | 4.3 | Mar 5 | 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 having a lifetime exceeding the original… Affected: 2023.1.4189 before 2025.3.14761; 2025.4.51 before 2025.4.10409 |
| CVE-2023-4509 | 4.3 | Apr 17 | It is possible for an API key to be logged in clear text in the audit log file after an invalid login attempt Affected: 2018.9.0 before 2023.4.296 |
| CVE-2022-2416 | 4.3 | Aug 2 | In affected versions of Octopus Deploy it is possible for a low privileged guest user to craft a request that allows enumeration/recon of an environment Affected: 2019.4.0 before 2022.4.9997; 2023.1.4189 before 2023.1.10235; 2023.2.2028 before 2023.2.10545 |
| CVE-2022-2346 | 4.3 | Aug 2 | In affected versions of Octopus Deploy it is possible for a low privileged guest user to interact with extension endpoints Affected: 2019.4.0 before 2022.4.9997; 2023.1.4189 before 2023.1.10235; 2023.2.2028 before 2023.2.10545 |
| CVE-2022-2258 | 4.3 | Mar 13 | In affected versions of Octopus Deploy it is possible for a user to view Tagsets without being explicitly assigned permissions to view these items Affected: 2019.1.0 before 2022.3.11098; 2022.4.791 before 2022.4.8463; 2023.1.4189 before 2023.1.9672; 2023.2.2028 |
| CVE-2022-2259 | 4.3 | Mar 13 | In affected versions of Octopus Deploy it is possible for a user to view Workerpools without being explicitly assigned permissions to view these items Affected: 2019.1.0 before 2022.3.11098; 2022.4.791 before 2022.4.8463; 2023.1.4189 before 2023.1.9672; 2023.2.2028 |
| CVE-2022-2760 | 4.3 | Sep 28 | In affected versions of Octopus Deploy it is possible to reveal the Space ID of spaces that the user does not have access to view in an error message when a resource is part of… Affected: 2019.5.7 before 2022.1.3180; 2022.2.0 before 2022.2.7965; 2022.3.0 before 2022.3.10405 |
| CVE-2020-16197 | 4.3 | Aug 25 | An issue was discovered in Octopus Deploy 3.4 Affected: 3.4.0 |
| CVE-2019-15698 | 4.3 | Aug 27 | In Octopus Deploy 2019.7.3 through 2019.7.9, in certain circumstances, an authenticated user with VariableView permissions could view sensitive values Affected: 2019.7.3 through 2019.7.9 |
Showing 37
