octopus octopus server
productUScpe:2.3:a:octopus:octopus_server:*:*:*:*:*:*:*:*
A product tracked in the threat graph; the vulnerabilities below are known to affect it.
by severity
6critical19high35medium0low
updated 2026-10-23
| ID | severity CVSS base severity and score (0–10). | EPSS FIRST.org probability this is exploited in the next 30 days, with its percentile rank among all CVEs. | exploitable On CISA's Known Exploited Vulnerabilities list, or a public exploit is on file. | patched Whether a fixed version is on file for an affecting range. | published | affected |
|---|
| CVE-2018-18850US | high8.8 | 12.5% (96th) | Exploit | ✓2018.9.1 | 2018-10-31 | 2 versions |
| CVE-2019-8944US | medium6.5 | 1.55% (75th) | — | ✓2019.1.8 | 2019-02-20 | 2018.11.0 → 2019.1.8 |
| CVE-2019-14525US | medium4.9 | 1.53% (75th) | — | ✓2019.7.6 | 2019-08-05 | 2019.7.0 → 2019.7.6 |
| CVE-2018-11320US | critical9.8 | 1.35% (71st) | — | ✗no fix | 2018-05-21 | 2018.4.4 → 2018.5.1 |
| CVE-2017-11348US | medium5.7 | 1.22% (68th) | — | ✗no fix | 2017-07-17 | 183 versions |
| CVE-2019-11632US | high8.1 | 1.15% (67th) | — | ✗no fix | 2019-05-01 | 2019.4.0 → 2019.4.5 |
| CVE-2022-2883US | high7.5 | 1.02% (63rd) | — | ✓2022.3.11043 | 2023-02-22 | 2 versions |
| CVE-2018-12089US | high7.5 | 0.91% (60th) | — | ✗no fix | 2018-06-11 | 2018.5.1 → 2018.5.7 |
| CVE-2022-2572US | critical9.8 | 0.91% (59th) | — | ✓2022.3.10586 | 2022-11-01 | 4 versions |
| CVE-2019-15698US | medium4.3 | 0.88% (59th) | — | ✗no fix | 2019-08-27 | 2019.7.3 → 2019.7.9 |
| CVE-2022-2074US | high7.5 | 0.87% (58th) | — | ✓2022.2.6872 | 2022-08-19 | 12 versions |
| CVE-2022-2778US | critical9.8 | 0.86% (58th) | — | ✓2022.2.8277 | 2022-09-30 | 3 versions |
| CVE-2022-1670US | high7.5OT elevated | 0.85% (58th) | — | ✓2022.1.53 | 2022-05-19 | 2 versions |
| CVE-2022-2075US | high7.5 | 0.76% (55th) | — | ✓2022.3.4953 | 2022-08-19 | 12 versions |
| CVE-2022-2049US | high7.5 | 0.76% (55th) | — | ✓2022.3.4953 | 2022-08-19 | 12 versions |
| CVE-2022-4009US | high8.8 | 0.72% (53rd) | — | ✓2022.2.8552 | 2023-03-16 | 3 versions |
| CVE-2022-2828US | medium6.5 | 0.65% (50th) | — | ✗no fix | 2022-10-13 | 3 versions |
| CVE-2022-2780US | high8.1OT elevated | 0.62% (49th) | — | ✓2022.2.7965 | 2022-10-14 | 3 versions |
| CVE-2021-31820US | high7.5OT elevated | 0.61% (49th) | — | ✓2021.1.7622 | 2021-08-18 | 3 versions |
| CVE-2022-2721US | high7.5 | 0.60% (48th) | — | ✓2022.2.7965 | 2022-11-25 | 2 versions |
| CVE-2022-2782US | critical9.1 | 0.59% (47th) | — | ✓2022.4.2898 | 2022-10-27 | 3 versions |
| CVE-2022-3460US | high7.5 | 0.57% (47th) | — | ✓2022.3.10750 | 2023-01-03 | 2 versions |
| CVE-2022-2508US | medium5.3 | 0.57% (46th) | — | ✓2022.2.8351 | 2022-10-27 | 4 versions |
| CVE-2022-23184US | medium6.1 | 0.56% (46th) | — | ✓2021.3.11057 | 2022-02-07 | 2 versions |
| CVE-2022-1881US | medium5.3 | 0.56% (46th) | — | ✓2022.1.2894 | 2022-07-15 | 4 versions |
| CVE-2022-2720US | medium5.3 | 0.55% (45th) | — | ✓2022.1.3154 | 2022-10-12 | 3 versions |
| CVE-2020-16197US | medium4.3 | 0.55% (45th) | — | ✗no fix | 2020-08-25 | = 3.4.0 |
| CVE-2022-1901US | medium5.3 | 0.55% (45th) | — | ✓2022.3.4953 | 2022-08-19 | 6 versions |
| CVE-2022-2760US | medium4.3 | 0.55% (45th) | — | ✓2022.3.10405 | 2022-09-28 | 3 versions |
| CVE-2022-30532US | medium5.3 | 0.54% (45th) | — | ✓2021.3.13021 | 2022-07-19 | 3 versions |
| CVE-2022-2528US | medium6.5OT elevated | 0.51% (42nd) | — | ✓2022.2.7718 | 2022-09-09 | 5 versions |
| CVE-2022-2258US | medium4.3 | 0.50% (42nd) | — | ✓2022.4.8463 | 2023-03-13 | 4 versions |
| CVE-2022-29890US | medium6.1 | 0.47% (39th) | — | ✓2021.3.13021 | 2022-07-15 | 4 versions |
| CVE-2022-4870US | medium5.3 | 0.45% (38th) | — | ✓2023.1.9879 | 2023-05-18 | 2 versions |
| CVE-2022-2259US | medium4.3 | 0.43% (37th) | — | ✓2022.4.8463 | 2023-03-13 | 4 versions |
| CVE-2024-9194US | critical9.8 | 0.43% (36th) | — | ✓2024.3.12766 | 2024-09-30 | 3 versions |
| CVE-2025-0588US | medium4.9 | 0.42% (36th) | — | ✓2024.3.13097 | 2025-02-11 | 2 versions |
| CVE-2022-2507US | medium5.3 | 0.42% (35th) | — | ✓2023.1.6715 | 2023-04-19 | 3 versions |
| CVE-2022-3614US | medium6.1OT elevated | 0.40% (33rd) | — | ✓2022.3.10750 | 2023-01-03 | 2 versions |
| CVE-2024-2975US | high7.5 | 0.39% (32nd) | — | ✓2023.4.8432 | 2024-04-09 | 3 versions |
| CVE-2022-4898US | medium5.4 | 0.39% (32nd) | — | ✓2022.4.8319 | 2023-01-31 | 3 versions |
| CVE-2023-1904US | high7.5 | 0.39% (31st) | — | ✓2023.2.13151 | 2023-12-14 | 3 versions |
| CVE-2025-0525US | high7.5 | 0.38% (30th) | — | ✓2024.3.13007 | 2025-02-11 | 2 versions |
| CVE-2025-0589US | medium5.3 | 0.37% (30th) | — | ✓2024.3.13071 | 2025-02-11 | 2 versions |
| CVE-2026-4881US | medium6.5OT elevated | 0.37% (29th) | — | ✓2025.4.10545 | 2026-06-04 | 2 versions |
| CVE-2025-0539US | high8.8 | 0.36% (29th) | — | ✓2024.4.7065 | 2025-04-10 | 2 versions |
| CVE-2025-0526US | medium5.4OT elevated | 0.35% (27th) | — | ✓2024.4.7091 | 2025-02-11 | 2 versions |
| CVE-2026-0704US | critical9.1 | 0.34% (27th) | — | ✓2025.3.14715 | 2026-02-25 | 2023.1.4189 → 2025.3.14715 |
| CVE-2022-2346US | medium4.3 | 0.34% (26th) | — | ✓2022.4.9997 | 2023-08-02 | 3 versions |
| CVE-2026-12702US | medium4.9 | 0.33% (25th) | — | ✓2026.1.11587 | 2026-07-24 | 2 versions |
showing 50 of 66