In Octopus Deploy before 2019.10.6, an authenticated user with TeamEdit permission could send a malformed Team API request that bypasses in…

published 2019-11-28 6y ago modified 2026-06-17 4mo ago also EUVD-2019-8997

cvss: 6.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.0%; EPSS 1.0% chance of exploitation in 30 days, percentile 62%
public exploits: 0; none known

In Octopus Deploy before 2019.10.6, an authenticated user with TeamEdit permission could send a malformed Team API request that bypasses input validation and causes an application level denial of service condition. (The fix for this was also backported to LTS 2019.9.8 and LTS 2019.6.14.)

Patch / fix

fixed in 1

octopus octopus_deploy 2019.6.14, 2019.9.8, 2019.10.7

Is CVE-2019-19376 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

Exploit prediction

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

CVSS scores

assigned by	version	score	vector
NVD	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD	2.0	4.0	AV:N/AC:L/Au:S/C:N/I:N/A:P

Classification

Weakness

CWE-20 Improper Input Validation
CWE-476 NULL Pointer Dereference

References

github.com /OctopusDeploy/Issues/issues/6005
third-party-advisory

Sources

CVE List CVE-2019-19376
NVD CVE-2019-19376

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.