In affected versions of Octopus Server, creating a user invitation writes the invitation code to the audit event log.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2026.2.13438, 2026.3.15829
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Octopus Server, a deployment automation product, is affected by a flaw where creating a user invitation records the invitation code in the audit event log. Users with appropriate permissions in a space linked to the invitation could read the code and potentially use it to gain higher privileges, depending on the permissions assigned to the invited user.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
In affected versions of Octopus Server, creating a user invitation writes the invitation code to the audit event log. When the invitation is linked to a space, a user in that space with appropriate permissions could read the code from the audit event. Successfully exploiting this by redeeming the unclaimed invitation could allow the user to escalate privileges however this is dependant on the permissions assigned for the invited user.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Octopus Deploy Octopus Server
From 2019.0.0 · fixed in 2026.2.13438; From 2026.3.0 · fixed in 2026.3.15829