CVE Tools

Octopus Deploy

31 CVEs tracked. None of them is in CISA KEV.

This hub aggregates every CVE we track for Octopus Deploy, a product in the devtools ci space. Use it to gauge the current risk picture and drill into individual advisories.

Octopus Deploy CVEs per month

Nov 2024 to Oct 2026. Point at a month, or focus the strip and use the arrow keys.
Octopus Deploy CVEs per month
MonthCVEs
2024-110
2024-120
2025-010
2025-020
2025-030
2025-040
2025-050
2025-060
2025-070
2025-080
2025-090
2025-100
2025-110
2025-120
2026-010
2026-020
2026-030
2026-040
2026-050
2026-060
2026-070
2026-080
2026-090
2026-100

Severity

How the 31 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.

  • High1239%
  • Medium1961%

Latest CVEs

The 15 most recently published vulnerabilities affecting Octopus Deploy.

  1. CVE-2023-2247In affected versions of Octopus Deploy it is possible to unmask variable secrets using the variable preview function5.3
  2. CVE-2022-2013In Octopus Server after version 2022.1.1495 and before 2022.1.2647 if private spaces were enabled via the experimental feature flag all new users would have access to the Script Console within thei...7.5
  3. CVE-2022-23184In affected Octopus Server versions when the server HTTP and HTTPS bindings are configured to localhost, Octopus Server will allow open redirects.6.1
  4. CVE-2021-26556When Octopus Server is installed using a custom folder location, folder ACLs are not set correctly and could lead to an unprivileged user using DLL side-loading to gain privileged access.7.8
  5. CVE-2020-26161In Octopus Deploy through 2020.4.2, an attacker could redirect users to an external site via a modified HTTP Host header.6.1
  6. CVE-2020-27155An issue was discovered in Octopus Deploy through 2020.4.4. If enabled, the websocket endpoint may allow an untrusted tentacle host to present itself as a trusted one.7.5
  7. CVE-2020-25825In Octopus Deploy 3.1.0 to 2020.4.0, certain scripts can reveal sensitive information to the user in the task logs.7.5
  8. CVE-2020-24566In Octopus Deploy 2020.3.x before 2020.3.4 and 2020.4.x before 2020.4.1, if an authenticated user creates a deployment or runbook process using Azure steps and sets the step's execution location to...7.5
  9. CVE-2020-14470In Octopus Deploy 2018.8.0 through 2019.x before 2019.12.2, an authenticated user with could trigger a deployment that leaks the Helm Chart repository password.6.5
  10. CVE-2020-12286In Octopus Deploy before 2019.12.9 and 2020 before 2020.1.12, the TaskView permission is not scoped to any dimension. For example, a scoped user who is scoped to only one tenant can view server tas...4.3
  11. CVE-2020-10678In Octopus Deploy before 2020.1.5, for customers running on-premises Active Directory linked to their Octopus server, an authenticated user can leverage a bug to escalate privileges.8.8
  12. CVE-2019-19376In Octopus Deploy before 2019.10.6, an authenticated user with TeamEdit permission could send a malformed Team API request that bypasses input validation and causes an application level denial of s...6.5
  13. CVE-2019-19375In Octopus Deploy before 2019.10.7, in a configuration where SSL offloading is enabled, the CSRF cookie was sometimes sent without the secure attribute. (The fix for this was backported to LTS vers...5.3
  14. CVE-2019-19084In Octopus Deploy 3.3.0 through 2019.10.4, an authenticated user with PackagePush permission to upload packages could upload a maliciously crafted package, triggering an exception that exposes unde...4.3
  15. CVE-2019-14525In 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 server configuration ...4.9

Product grouping is registry-driven, with AI assist and human review. How it works