Skip to content
Fencer Intel
high 7.5

CVE-2016-5360 in the critical feed json

HAproxy 1.6.x before 1.6.6, when a deny comes from a reqdeny rule, allows remote attackers to cause a denial of service (uninitialized memo…

published 2016-06-30 10 y ago modified 2026-06-17 4 mo ago also EUVD-2016-6311

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
42.8%
EPSS 42.8% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

HAproxy 1.6.x before 1.6.6, when a deny comes from a reqdeny rule, allows remote attackers to cause a denial of service (uninitialized memory access and crash) or possibly have unspecified other impact via unknown vectors.

Patch / fix

  • haproxy Debian 14, Debian 13, Debian 12 1.6.5-2

debian advisories DEBIAN-CVE-2016-5360

  • haproxy Ubuntu 16.04 LTS 1.6.3-1ubuntu0.1

ubuntu advisories UBUNTU-CVE-2016-5360

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

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-5360 updated cvss 4.3

haproxy: denial of service via reqdeny

  • Red Hat Enterprise Linux 6 haproxy Red Hat Enterprise Linux 7 haproxy Red Hat OpenShift Enterprise 2 haproxy
    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

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

CVSS scores

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

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

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.