How severe is CVE-2022-2013?

CVE-2022-2013 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2022-2013 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (54th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2022-2013?

CVE-2022-2013 affects Octopus Octopus Deploy. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2022-2013?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2022-2013 published?

CVE-2022-2013 was published on 2022-06-13 and last updated on 2026-06-17.

CVE-2022-2013

CVE-2022-2013 is a high-severity vulnerability in Octopus Octopus Deploy with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 4.3
EPSS exploit prediction: 1% (54th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Octopus Octopus Deploy
Published: 2022-06-13
Last modified: 2026-06-17

Description

In 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 their private space.

Frequently asked questions

What is CVE-2022-2013?: In 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 their private space.
How severe is CVE-2022-2013?: CVE-2022-2013 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2022-2013 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (54th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-2013?: CVE-2022-2013 affects Octopus Octopus Deploy. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2022-2013?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2022-2013 published?: CVE-2022-2013 was published on 2022-06-13 and last updated on 2026-06-17.

References

https://advisories.octopus.com/post/2022/sa2022-05/

Affected products (1)

cpe:2.3:a:octopus:octopus_deploy:*:*:*:*:*:*:*:*

More vulnerabilities in Octopus Octopus Deploy

CVE-2020-10678 — High (CVSS 8.8): In Octopus Deploy before 2020.1.5, for customers running on-premises Active Directory linked to their Octopus server,…
CVE-2018-5706 — High (CVSS 8.8): An issue was discovered in Octopus Deploy before 4.1.9. Any user with user editing permissions can modify teams to give…
CVE-2018-4862 — High (CVSS 8.8): In Octopus Deploy versions 3.2.11 - 4.1.5 (fixed in 4.1.6), an authenticated user with ProcessEdit permission could…
CVE-2017-17665 — High (CVSS 8.8): In Octopus Deploy before 4.1.3, the machine update process doesn't check that the user has access to all environments.…
CVE-2019-11632 — High (CVSS 8.1): In Octopus Deploy 2019.1.0 through 2019.3.1 and 2019.4.0 through 2019.4.5, an authenticated user with the…
CVE-2021-26556 — High (CVSS 7.8): When Octopus Server is installed using a custom folder location, folder ACLs are not set correctly and could lead to an…

All CVEs affecting Octopus Octopus Deploy →