Apache HTTP Server up to 2.4.68 mod_proxy_html out-of-bounds write

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 10.0 | $25k-$100k | 0.76- |
Summary
A vulnerability was found in Apache HTTP Server up to 2.4.68. It has been classified as very critical. Impacted is an unknown function of the component mod_proxy_html. Performing a manipulation results in out-of-bounds write. This vulnerability is known as CVE-2026-56449. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability, which was classified as very critical, was found in Apache HTTP Server up to 2.4.68. This affects an unknown code block of the component mod_proxy_html. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. CWE is classifying the issue as CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Out-of-bounds Write vulnerability in Apache HTTP Server's mod_proxy_html with crafted HTTP response bodies. This issue affects Apache HTTP Server: from 2.4.0 through 2.4.68.
The advisory is shared at httpd.apache.org. This vulnerability is uniquely identified as CVE-2026-56449 since 06/22/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $25k-$100k at the moment (estimation calculated on 10/01/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 2.4.0
- 2.4.1
- 2.4.2
- 2.4.3
- 2.4.4
- 2.4.5
- 2.4.6
- 2.4.7
- 2.4.8
- 2.4.9
- 2.4.10
- 2.4.11
- 2.4.12
- 2.4.13
- 2.4.14
- 2.4.15
- 2.4.16
- 2.4.17
- 2.4.18
- 2.4.19
- 2.4.20
- 2.4.21
- 2.4.22
- 2.4.23
- 2.4.24
- 2.4.25
- 2.4.26
- 2.4.27
- 2.4.28
- 2.4.29
- 2.4.30
- 2.4.31
- 2.4.32
- 2.4.33
- 2.4.34
- 2.4.35
- 2.4.36
- 2.4.37
- 2.4.38
- 2.4.39
- 2.4.40
- 2.4.41
- 2.4.42
- 2.4.43
- 2.4.44
- 2.4.45
- 2.4.46
- 2.4.47
- 2.4.48
- 2.4.49
- 2.4.50
- 2.4.51
- 2.4.52
- 2.4.53
- 2.4.54
- 2.4.55
- 2.4.56
- 2.4.57
- 2.4.58
- 2.4.59
- 2.4.60
- 2.4.61
- 2.4.62
- 2.4.63
- 2.4.64
- 2.4.65
- 2.4.66
- 2.4.67
- 2.4.68
License
Website
- Vendor: https://www.apache.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 10.0
VulDB Base Score: 10.0
VulDB Temp Score: 10.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Out-of-bounds writeCWE: CWE-787 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
06/22/2026 CVE reserved10/01/2026 Advisory disclosed
10/01/2026 VulDB entry created
10/01/2026 VulDB entry last update
Sources
Vendor: apache.orgAdvisory: httpd.apache.org
Status: Confirmed
CVE: CVE-2026-56449 (🔒)
GCVE (CVE): GCVE-0-2026-56449
GCVE (VulDB): GCVE-100-412725
Entry
Created: 10/01/2026 18:38Changes: 10/01/2026 18:38 (53)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.