Skip to content
Fencer Intel
high 8.8

CVE-2018-18850 in the critical feed json

In Octopus Deploy 2018.8.0 through 2018.9.x before 2018.9.1, an authenticated user with permission to modify deployment processes could upl…

published 8y ago modified 4mo ago also EUVD-2018-10564

cvss
8.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
12.5%
EPSS 12.5% chance of exploitation in 30 days, percentile 96%
public exploits
1
Metasploit

Summary

In Octopus Deploy 2018.8.0 through 2018.9.x before 2018.9.1, an authenticated user with permission to modify deployment processes could upload a maliciously crafted YAML configuration, potentially allowing for remote execution of arbitrary code, running in the same context as the Octopus Server (for self-hosted installations by default, SYSTEM).

Patch / fix

  • octopus octopus_server 2018.9.1

Is CVE-2018-18850 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit exploit/windows/http/octopusdeploy_deploy)
  2. Published

Exploit prediction

12.48% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
NVD 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 9.0 AV:N/AC:L/Au:S/C:C/I:C/A:C

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.