Vulnerability · CVE-2018-20615
An out-of-bounds read issue was discovered in the HTTP/2 protocol decoder in HAProxy 1.8.x and 1.9.x through 1.9.0 which can result in a crash.
Published Mar 21, 2019 · catalog updated Jun 17, 2026 · An out-of-bounds read issue
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-20615. EPSS is 4.46%. Act only if a listed version of An out-of-bounds read issue 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 out-of-bounds read issue).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-26081 · Medium
- CVE-2026-26080 · Low
- CVE-2026-55204 · High
- CVE-2026-55203 · Critical
- CVE-2026-33555 · Medium
- Severity
- High7.5
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 4.46%
- Remediation
- Version ranges on file
- Affected products
- cpe haproxy/haproxy
An out-of-bounds read issue was discovered in the HTTP/2 protocol decoder in HAProxy 1.8.x and 1.9.x through 1.9.0 which can result in a crash. The processing of the PRIORITY flag in a HEADERS frame requires 5 extra bytes, and while these bytes are skipped, the total frame length was not re-checked to make sure they were present in the frame.
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/haproxy1.9.0
- cpe haproxy/haproxy>= 1.8.0, <= 1.8.19
How to fix CVE-2018-20615
Upgrade
CVE-2018-20615 lists a fix boundary at 1.8.19. Compare the installed build with that boundary before you change production.
Version check
Affected <= 1.8.19
Advisory
Open the cve_org record and follow its fix.
Official advisories
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-20615. EPSS is 4.46%. Act only if a listed version of An out-of-bounds read issue is installed.
Which versions are affected?
Compare what you have installed with 1.9.0, >= 1.8.0, <= 1.8.19. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-125: Out-of-bounds Read. EPSS 4.46%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
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.
Mar 21, 2019 · Monitored products — high
Detected
An out-of-bounds read issue was discovered in the HTTP/2 protocol decoder in HAProxy 1.8.x and 1.9.x through 1.9.0 which can result in a crash. The processing of the PRIORITY flag in a HEADERS frame requires 5 extra bytes, and while these bytes are skipped, the total frame length was not re-checked to make sure they were present in the frame.
Jun 17, 2026 · Monitored products — high
Updated
An out-of-bounds read issue was discovered in the HTTP/2 protocol decoder in HAProxy 1.8.x and 1.9.x through 1.9.0 which can result in a crash. The processing of the PRIORITY flag in a HEADERS frame requires 5 extra bytes, and while these bytes are skipped, the total frame length was not re-checked to make sure they were present in the frame.
Sources
- CVE.orgVulnerability recordCVE-2018-20615
Official CVE identifier
cve.org - Monitored products — highVendor advisoryCVE-2018-20615
An out-of-bounds read issue was discovered in the HTTP/2 protocol decoder in HAProxy 1.8.x and 1.9.x through 1.9.0 which can result in a crash. The processing of the PRIORITY flag in a HEADERS frame requires 5 extra bytes, and while these bytes are skipped, the total frame length was not re-checked to make sure they were present in the frame.
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