ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2018-10184

An issue was discovered in HAProxy before 1.8.8.

Published May 9, 2018 · catalog updated Jun 17, 2026 · An issue was discovered

Last checked Nov 5, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2018-10184. EPSS is 8.15%. Act only if a listed version of An issue was discovered is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (An issue was discovered).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
8.15%
Remediation
Version ranges on file
Affected products
cpe haproxy/haproxy · cpe redhat/enterprise linux

An issue was discovered in HAProxy before 1.8.8. The incoming H2 frame length was checked against the max_frame_size setting instead of being checked against the bufsize. The max_frame_size only applies to outgoing traffic and not to incoming, so if a large enough frame size is advertised in the SETTINGS frame, a wrapped frame will be defragmented into a temporary allocated buffer where the second fragment may overflow the heap by up to 16 kB. It is very unlikely that this can be exploited for code execution given that buffers are very short lived and their addresses not realistically predictable in production, but the likelihood of an immediate crash is absolutely certain.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe haproxy/haproxy< 1.8.8
  • cpe redhat/enterprise linux7.0
  • cpe redhat/enterprise linux7.3
  • cpe redhat/enterprise linux7.4
  • cpe redhat/enterprise linux7.5

How to fix CVE-2018-10184

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2018-10184. EPSS is 8.15%. Act only if a listed version of An issue was discovered is installed.

Which versions are affected?

Compare what you have installed with redhat/enterprise linux 7.0; redhat/enterprise linux 7.3; redhat/enterprise linux 7.4; redhat/enterprise linux 7.5. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-119: Buffer Overflow. EPSS 8.15%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

HAProxy security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. May 9, 2018 · Monitored products — high

    Detected

    An issue was discovered in HAProxy before 1.8.8. The incoming H2 frame length was checked against the max_frame_size setting instead of being checked against the bufsize. The max_frame_size only applies to outgoing traffic and not to incoming, so if a large enough frame size is advertised in the SETTINGS frame, a wrapped frame will be defragmented into a temporary allocated buffer where the second

  2. Jun 17, 2026 · Monitored products — high

    Updated

    An issue was discovered in HAProxy before 1.8.8. The incoming H2 frame length was checked against the max_frame_size setting instead of being checked against the bufsize. The max_frame_size only applies to outgoing traffic and not to incoming, so if a large enough frame size is advertised in the SETTINGS frame, a wrapped frame will be defragmented into a temporary allocated buffer where the second

Sources

  • CVE.orgVulnerability recordCVE-2018-10184

    Official CVE identifier

    cve.org
  • Monitored products — highVendor advisoryCVE-2018-10184

    An issue was discovered in HAProxy before 1.8.8. The incoming H2 frame length was checked against the max_frame_size setting instead of being checked against the bufsize. The max_frame_size only applies to outgoing traffic and not to incoming, so if a large enough frame size is advertised in the SETTINGS frame, a wrapped frame will be defragmented into a temporary allocated buffer where the second

    nvd.nist.gov

References

Freshness

Last verified in this catalog Nov 5, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • CVE.orgNov 4, 2026
  • Monitored products — highNov 2, 2026