VYPR
← All advisories
High severity7.3NVD Advisory· Published Jun 8, 2026· Updated Jun 8, 2026

CVE-2026-44185

CVE-2026-44185

Description

Apache HTTP Server 2.4.0-2.4.67 has a buffer over-read vulnerability in outbound OCSP requests, potentially leading to information disclosure.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Apache HTTP Server 2.4.0-2.4.67 has a buffer over-read vulnerability in outbound OCSP requests, potentially leading to information disclosure.

Vulnerability

A buffer over-read vulnerability exists in Apache HTTP Server versions 2.4.0 through 2.4.67. This issue is triggered when the server makes outbound OCSP (Online Certificate Status Protocol) requests to an attacker-controlled OCSP server [1].

Exploitation

An attacker can exploit this vulnerability by controlling an OCSP server that Apache HTTP Server communicates with. The vulnerability is triggered when the affected Apache HTTP Server instance makes an outbound OCSP request to this malicious server. No specific authentication or user interaction is mentioned as required in the available references.

Impact

Successful exploitation of this buffer over-read vulnerability could lead to information disclosure. The exact scope and privilege level of the compromise are not detailed in the available references, but typically buffer over-reads can lead to disclosure of sensitive memory contents [1].

Mitigation

Users are recommended to upgrade to Apache HTTP Server version 2.4.68 or later. Version 2.4.68 was released on 2026-06-08 and includes a fix for this issue [1].

References
  1. Apache HTTP Server 2.4 vulnerabilities

AI Insight generated on Jun 8, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

1
35c6e405390e

cookie reqest header counting (#324)

https://github.com/icing/mod_h2Stefan EissingMay 27, 2026via body-scan
commit
1 file changed · +4 −0
  • mod_http2/h2_util.c+4 −0 modified
    @@ -1708,6 +1708,8 @@ static apr_status_t req_add_header(apr_table_t *headers, apr_pool_t *pool,
              && !ap_cstr_casecmpn("cookie", (const char *)nv->name, nv->namelen)) {
         existing = apr_table_get(headers, "cookie");
         if (existing) {
+            if (!nv->valuelen)
+                return APR_SUCCESS;
             /* Cookie header come separately in HTTP/2, but need
              * to be merged by "; " (instead of default ", ")
              */
@@ -1719,6 +1721,8 @@ static apr_status_t req_add_header(apr_table_t *headers, apr_pool_t *pool,
             apr_table_setn(headers, "Cookie",
                            apr_psprintf(pool, "%s; %.*s", existing,
                                         (int)nv->valuelen, nv->value));
+            /* Treat the merge as an "add" to not escape LimitRequestFields */
+            *pwas_added = 1;
             return APR_SUCCESS;
         }
     }

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

1