Server
by Octopus
Source repositories
CVEs (79)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2026-12702 | Med | 0.32 | 4.9 | 0.00 | Jul 24, 2026 | In affected versions of Octopus Deploy Insufficient checks on the project trigger actions allows an unauthorized user to trigger a deployment. | ||
| CVE-2025-0588 | Med | 0.32 | 4.9 | 0.00 | Feb 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. By submitting a specifically crafted referrer header the user could ensure that all subsequent server responses would return 500 errors… | ||
| CVE-2019-14525 | Med | 0.32 | 4.9 | 0.02 | Aug 5, 2019 | 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 server configuration page or making an API call. | ||
| CVE-2026-3237 | Med | 0.28 | 4.3 | 0.00 | Mar 17, 2026 | 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 an API endpoint that had incorrect permission validation. It was not possible to expose the signing… | ||
| CVE-2026-3236 | Med | 0.28 | 4.3 | 0.00 | Mar 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 having a lifetime exceeding the original API key used to mint the access token. | ||
| CVE-2023-4509 | Med | 0.28 | 4.3 | 0.00 | Apr 18, 2024 | It is possible for an API key to be logged in clear text in the audit log file after an invalid login attempt. | ||
| CVE-2022-2259 | Med | 0.28 | 4.3 | 0.00 | Mar 13, 2023 | In affected versions of Octopus Deploy it is possible for a user to view Workerpools without being explicitly assigned permissions to view these items | ||
| CVE-2022-2258 | Med | 0.28 | 4.3 | 0.01 | Mar 13, 2023 | In affected versions of Octopus Deploy it is possible for a user to view Tagsets without being explicitly assigned permissions to view these items | ||
| CVE-2022-2760 | Med | 0.28 | 4.3 | 0.00 | Sep 28, 2022 | 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 another Space. | ||
| CVE-2022-1502 | Med | 0.28 | 4.3 | 0.01 | May 4, 2022 | Permissions were not properly verified in the API on projects using version control in Git. This allowed projects to be modified by users with only ProjectView permissions. | ||
| CVE-2021-31818 | Med | 0.28 | 4.3 | 0.01 | Jun 17, 2021 | Affected versions of Octopus Server are prone to an authenticated SQL injection vulnerability in the Events REST API because user supplied data in the API request isn’t parameterised correctly. Exploiting this vulnerability could allow unauthorised access to database tables. | ||
| CVE-2020-16197 | Med | 0.28 | 4.3 | 0.01 | Aug 25, 2020 | An issue was discovered in Octopus Deploy 3.4. A deployment target can be configured with an Account or Certificate that is outside the scope of the deployment target. An authorised user can potentially use a certificate that they are not in scope to use. An authorised user is… | ||
| CVE-2019-15698 | Med | 0.28 | 4.3 | 0.01 | Aug 27, 2019 | In Octopus Deploy 2019.7.3 through 2019.7.9, in certain circumstances, an authenticated user with VariableView permissions could view sensitive values. This is fixed in 2019.7.10. | ||
| CVE-2024-4456 | Med | 0.27 | 4.1 | 0.00 | May 8, 2024 | In affected versions of Octopus Server with certain access levels it was possible to embed a Cross-Site Scripting payload on the audit page. | ||
| CVE-2023-1904 | Med | 0.27 | 4.2 | 0.00 | Dec 14, 2023 | In affected versions of Octopus Server it is possible for the OpenID client secret to be logged in clear text during the configuration of Octopus Server. | ||
| CVE-2024-4226 | Low | 0.23 | 3.5 | 0.00 | Apr 30, 2024 | It was identified that in certain versions of Octopus Server, that a user created with no permissions could view all users, user roles and permissions. This functionality was removed in versions of Octopus Server after the fixed versions listed. | ||
| CVE-2024-1656 | Low | 0.17 | 2.6 | 0.00 | Sep 11, 2024 | Affected versions of Octopus Server had a weak content security policy. | ||
| CVE-2024-7998 | Low | 0.17 | 2.6 | 0.00 | Aug 21, 2024 | In affected versions of Octopus Server OIDC cookies were using the wrong expiration time which could result in them using the maximum lifespan. | ||
| CVE-2024-4811 | Low | 0.14 | 2.2 | 0.00 | Jul 25, 2024 | In affected versions of Octopus Server under certain conditions, a user with specific role assignments can access restricted project artifacts. |
- risk 0.32cvss 4.9epss 0.00
In affected versions of Octopus Deploy Insufficient checks on the project trigger actions allows an unauthorized user to trigger a deployment.
- risk 0.32cvss 4.9epss 0.00
In affected versions of Octopus Server it was possible for a user with sufficient access to set custom headers in all server responses. By submitting a specifically crafted referrer header the user could ensure that all subsequent server responses would return 500 errors…
- risk 0.32cvss 4.9epss 0.02
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 server configuration page or making an API call.
- risk 0.28cvss 4.3epss 0.00
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 an API endpoint that had incorrect permission validation. It was not possible to expose the signing…
- risk 0.28cvss 4.3epss 0.00
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 API key used to mint the access token.
- risk 0.28cvss 4.3epss 0.00
It is possible for an API key to be logged in clear text in the audit log file after an invalid login attempt.
- risk 0.28cvss 4.3epss 0.00
In affected versions of Octopus Deploy it is possible for a user to view Workerpools without being explicitly assigned permissions to view these items
- risk 0.28cvss 4.3epss 0.01
In affected versions of Octopus Deploy it is possible for a user to view Tagsets without being explicitly assigned permissions to view these items
- risk 0.28cvss 4.3epss 0.00
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 another Space.
- risk 0.28cvss 4.3epss 0.01
Permissions were not properly verified in the API on projects using version control in Git. This allowed projects to be modified by users with only ProjectView permissions.
- risk 0.28cvss 4.3epss 0.01
Affected versions of Octopus Server are prone to an authenticated SQL injection vulnerability in the Events REST API because user supplied data in the API request isn’t parameterised correctly. Exploiting this vulnerability could allow unauthorised access to database tables.
- risk 0.28cvss 4.3epss 0.01
An issue was discovered in Octopus Deploy 3.4. A deployment target can be configured with an Account or Certificate that is outside the scope of the deployment target. An authorised user can potentially use a certificate that they are not in scope to use. An authorised user is…
- risk 0.28cvss 4.3epss 0.01
In Octopus Deploy 2019.7.3 through 2019.7.9, in certain circumstances, an authenticated user with VariableView permissions could view sensitive values. This is fixed in 2019.7.10.
- risk 0.27cvss 4.1epss 0.00
In affected versions of Octopus Server with certain access levels it was possible to embed a Cross-Site Scripting payload on the audit page.
- risk 0.27cvss 4.2epss 0.00
In affected versions of Octopus Server it is possible for the OpenID client secret to be logged in clear text during the configuration of Octopus Server.
- risk 0.23cvss 3.5epss 0.00
It was identified that in certain versions of Octopus Server, that a user created with no permissions could view all users, user roles and permissions. This functionality was removed in versions of Octopus Server after the fixed versions listed.
- risk 0.17cvss 2.6epss 0.00
Affected versions of Octopus Server had a weak content security policy.
- risk 0.17cvss 2.6epss 0.00
In affected versions of Octopus Server OIDC cookies were using the wrong expiration time which could result in them using the maximum lifespan.
- risk 0.14cvss 2.2epss 0.00
In affected versions of Octopus Server under certain conditions, a user with specific role assignments can access restricted project artifacts.
Page 4 of 4