openshift before versions 3.3.1.11, 3.2.1.23, 3.4 is vulnerable to a flaw when a volume fails to detach, which causes the delete operation…

published 2018-04-16 8 y ago modified 2026-06-17 4 mo ago also EUVD-2016-10396

cvss: 4.3; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.2%; EPSS 1.2% chance of exploitation in 30 days, percentile 69%
public exploits: 0; none known

openshift before versions 3.3.1.11, 3.2.1.23, 3.4 is vulnerable to a flaw when a volume fails to detach, which causes the delete operation to fail with 'VolumeInUse' error. Since the delete operation is retried every 30 seconds for each volume, this could lead to a denial of service attack as the number of API requests being sent to the cloud-provider exceeds the API's rate-limit.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2016-9592 updated 2026-06-30 cvss 4.3

openshift: Failing to detach a volume causes DoS by retrying to perform delete

Red Hat OpenShift Enterprise 3 Security
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

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

CVSS scores

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

Affected products

unspecified openshift

Classification

Weakness

CWE-460 Improper Cleanup on Thrown Exception
CWE-399 Resource Management Errors

References

bugzilla.redhat.com /show_bug.cgi?id=CVE-2016-9592
issue-tracking, third-party-advisory
securityfocus.com /bid/94991
vdb-entry, third-party-advisory

Sources

CVE List CVE-2016-9592
NVD CVE-2016-9592

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.

Summary