聚合 NVD、CVE 及多源情資，深度解析 RCE 等高危風險。系統整合 CVSS 與 EPSS 模型，動態追蹤 Exploit 資源與 PoC 公開狀態，研判可利用性。結合官方修補與修復方案，優化漏洞管理優先級，縮短回應週期，保障資產安全。
指派機構（CNA / 來源）：[email protected] 移除此篩選
| CVE | 描述 | 最高 CVSS | EPSS % | 公開時間 | 更新時間 |
|---|---|---|---|---|---|
| CVE-2025-0513 | In affected versions of Octopus Server error messages were handled unsafely on the error page. If an adversary could control any part of the error message they could embed code which may impact the user viewing the error message. | 1.8 | 0.22% | 2025-02-11 | 2026-06-17 |
| CVE-2024-4811 | In affected versions of Octopus Server under certain conditions, a user with specific role assignments can access restricted project artifacts. | 2.2 | 0.24% | 2024-07-25 | 2026-06-17 |
| CVE-2026-3237 | 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 keys using this vulnerability. | 2.3 | 0.15% | 2026-03-17 | 2026-06-17 |
| CVE-2026-3236 | 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. | 2.3 | 0.15% | 2026-03-05 | 2026-06-17 |
| CVE-2025-0526 | In affected versions of Octopus Deploy it was possible to upload files to unexpected locations on the host using an API endpoint. The field lacked validation which could potentially result in ways to circumvent expected workflows. | 2.3 | 0.32% | 2025-02-11 | 2026-06-17 |
| CVE-2025-0525 | In affected versions of Octopus Server the preview import feature could be leveraged to identify the existence of a target file. This could provide an adversary with information that may aid in further attacks against the server. | 2.3 | 0.34% | 2025-02-11 | 2026-06-17 |
| CVE-2024-7998 | In affected versions of Octopus Server OIDC cookies were using the wrong expiration time which could result in them using the maximum lifespan. | 2.6 | 0.23% | 2024-08-21 | 2026-06-17 |
| CVE-2024-1656 | Affected versions of Octopus Server had a weak content security policy. | 2.6 | 0.23% | 2024-09-11 | 2026-06-17 |
| CVE-2024-4226 | 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. | 3.5 | 0.30% | 2024-04-29 | 2026-06-17 |
| CVE-2024-4456 | In affected versions of Octopus Server with certain access levels it was possible to embed a Cross-Site Scripting payload on the audit page. | 4.1 | 0.26% | 2024-05-07 | 2026-06-17 |
| CVE-2023-1904 | 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. | 4.2 | 0.39% | 2023-12-14 | 2026-06-17 |
| CVE-2023-4509 | It is possible for an API key to be logged in clear text in the audit log file after an invalid login attempt. | 4.3 | 0.23% | 2024-04-17 | 2026-06-17 |
| CVE-2022-2760 | 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. | 4.3 | 0.43% | 2022-09-28 | 2026-06-17 |
| CVE-2022-2259 | In affected versions of Octopus Deploy it is possible for a user to view Workerpools without being explicitly assigned permissions to view these items | 4.3 | 0.43% | 2023-03-13 | 2026-06-17 |
| CVE-2022-2258 | In affected versions of Octopus Deploy it is possible for a user to view Tagsets without being explicitly assigned permissions to view these items | 4.3 | 0.50% | 2023-03-13 | 2026-06-17 |
| CVE-2022-1502 | 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. | 4.3 | 0.49% | 2022-05-04 | 2026-06-17 |
| CVE-2021-31818 | 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. | 4.3 | 0.62% | 2021-06-17 | 2026-06-16 |
| CVE-2023-2247 | In affected versions of Octopus Deploy it is possible to unmask variable secrets using the variable preview function | 5.3 | 0.45% | 2023-05-02 | 2026-06-17 |
| CVE-2022-4870 | In affected versions of Octopus Deploy it is possible to discover network details via error message | 5.3 | 0.45% | 2023-05-17 | 2026-06-17 |
| CVE-2022-30532 | In affected versions of Octopus Deploy, there is no logging of changes to artifacts within Octopus Deploy. | 5.3 | 0.46% | 2022-07-19 | 2026-06-17 |