GHSA-jrpc-7vxp-69p6: http4k `reverseProxy()` Defaulted To Substring (`Contains`) Vulnerability

MODERATE
CWE-444
Published
Advisory Summary

GHSA-jrpc-7vxp-69p6 is a MODERATE `reverseproxy()` defaulted to substring (`contains`) vulnerability (CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')) affecting http4k libraries in the Maven ecosystem. The issue involves `reverseproxy()` defaulted to substring (`contains`) matching on `host`; tightened to `exact`. Remediation is available by upgrading affected packages to version 6.49.0.0, 5.42.0.0, 4.51.0.0.

GHSA-jrpc-7vxp-69p6 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-jrpc-7vxp-69p6
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
Affected Product http4k
Package Ecosystem Maven
Published Date
Last Updated

How to Fix GHSA-jrpc-7vxp-69p6

To remediate this vulnerability, upgrade all affected http4k dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.http4k:http4k-core fixed: 6.49.0.0
<dependency>
    <groupId>org.http4k</groupId>
    <artifactId>http4k-core</artifactId>
    <version>6.49.0.0</version>
</dependency>
org.http4k:http4k-core fixed: 5.42.0.0
<dependency>
    <groupId>org.http4k</groupId>
    <artifactId>http4k-core</artifactId>
    <version>5.42.0.0</version>
</dependency>
org.http4k:http4k-core fixed: 4.51.0.0
<dependency>
    <groupId>org.http4k</groupId>
    <artifactId>http4k-core</artifactId>
    <version>4.51.0.0</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=org.http4k

How to Check if You Are Affected

To determine whether your Java application is affected by GHSA-jrpc-7vxp-69p6, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.http4k

Analyze the terminal output to locate any version of http4k in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 6.49.0.0), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.http4k command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling'), where the product acts as an intermediary http agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed http requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination. In http4k, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact `reverseProxy()` and `reverseProxyRouting()` matched configured vhosts by substring on the `Host` header (`Contains` matcher) by default. The intended use of these functions in http4k is **outbound dispatch** (e.g. matching AWS service subdomains, per the `Contains` docstring) and **test-time composition** of fake backend networks. In either of those contexts the matched `Host` is set by the calling application, not by an external attacker, so the loose match has no exploit surface. If, however, `reverseProxy()` was deployed as a public-facing inbound HTTP handler — which the function technically supports but is not the documented intent — an external attacker could send `Host: admin.evil.com` and reach a vhost configured as `admin`, bypassing routing-based authorization. The `Contains` matcher's docstring explicitly documented this loose behaviour, but because `Contains` was the default, callers who never read the matcher docs would still get the loose behaviour. **Who is affected:** only deployments using `reverseProxy()` / `reverseProxyRouting()` as a public-facing inbound HTTP handler with two or more configured virtual hosts. The intended outbound / test-time usage is unaffected. If you *did* deploy `reverseProxy()` inbound and rely on multi-vhost routing for authorization, treat upgrade as urgent. ### Patches | Line | Fixed in | Edition | |------|----------|---------| | v6.x (Community) | **6.49.0.0** | Community | | v5.x (LTS) | **5.42.0.0** | Enterprise — contact [enterprise@http4k.org](mailto:enterprise@http4k.org) (if `reverseProxy()` is present in your v5.x line) | | v4.x (LTS) | **4.51.0.0** | Enterprise — contact [enterprise@http4k.org](mailto:enterprise@http4k.org) (if `reverseProxy()` is present in your v4.x line) | The fix changes the default matcher to `Exact`. Existing callers that genuinely need substring matching (e.g. AWS subdomain dispatch) must explicitly pass `matcher = Contains`. ### Workarounds For deployments that cannot upgrade immediately: wrap your `reverseProxy()` with a host-allow-list filter that requires an exact match against expected vhost names before delegating.

GHSA-jrpc-7vxp-69p6 Affected http4k Versions

3 component(s)
Fixed Versions:
6.49.0.05.42.0.04.51.0.0
Product / Package Ecosystem Affected Versions Fixed Version
org.http4k:http4k-core
Maven
≥ 6.0.0.0
< 6.49.0.0
6.49.0.0
org.http4k:http4k-core
Maven
≥ 5.0.0.0
< 5.42.0.0
5.42.0.0
org.http4k:http4k-core
Maven
< 4.51.0.0
4.51.0.0

References

Frequently Asked Questions

What is GHSA-jrpc-7vxp-69p6?
GHSA-jrpc-7vxp-69p6 is a security vulnerability in http4k involving `reverseProxy()` defaulted to substring (`Contains`) matching on `Host`; tightened to `Exact` under CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling').
Which http4k versions are affected?
Affected versions include releases prior to 6.49.0.0, 5.42.0.0, 4.51.0.0 across affected packages: org.http4k:http4k-core.
What version fixes GHSA-jrpc-7vxp-69p6?
Upgrading to 6.49.0.0, 5.42.0.0, 4.51.0.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is http4k-core affected?
Yes, org.http4k:http4k-core is affected in releases prior to 6.49.0.0, 5.42.0.0, 4.51.0.0. Upgrade your dependency to 6.49.0.0, 5.42.0.0, 4.51.0.0 or later.
What CWE is associated with GHSA-jrpc-7vxp-69p6?
GHSA-jrpc-7vxp-69p6 is classified under CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') (The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.).
How can I check Maven dependencies for GHSA-jrpc-7vxp-69p6?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.http4k'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-jrpc-7vxp-69p6",
  "modified" : "2026-09-24T14:57:44Z",
  "published" : "2026-06-19T21:15:59Z",
  "aliases" : [ ],
  "summary" : "http4k: `reverseProxy()` defaulted to substring (`Contains`) matching on `Host`; tightened to `Exact`",
  "details" : "### Impact\n\n`reverseProxy()` and `reverseProxyRouting()` matched configured vhosts by substring on the `Host` header (`Contains` matcher) by default. The intended use of these functions in http4k is **outbound dispatch** (e.g. matching AWS service subdomains, per the `Contains` docstring) and **test-time composition** of fake backend networks. In either of those contexts the matched `Host` is set by the calling application, not by an external attacker, so the loose match has no exploit surface.\n\nIf, however, `reverseProxy()` was deployed as a public-facing inbound HTTP handler — which the function technically supports but is not the documented intent — an external attacker could send `Host: admin.evil.com` and reach a vhost configured as `admin`, bypassing routing-based authorization.\n\nThe `Contains` matcher's docstring explicitly documented this loose behaviour, but because `Contains` was the default, callers who never read the matcher docs would still get the loose behaviour.\n\n**Who is affected:** only deployments using `reverseProxy()` / `reverseProxyRouting()` as a public-facing inbound HTTP handler with two or more configured virtual hosts. The intended outbound / test-time usage is unaffected. If you *did* deploy `reverseProxy()` inbound and rely on multi-vhost routing for authorization, treat upgrade as urgent.\n\n### Patches\n\n| Line | Fixed in | Edition |\n|------|----------|---------|\n| v6.x (Community) | **6.49.0.0** | Community |\n| v5.x (LTS) | **5.42.0.0** | Enterprise — contact [enterprise@http4k.org](mailto:enterprise@http4k.org) (if `reverseProxy()` is present in your v5.x line) |\n| v4.x (LTS) | **4.51.0.0** | Enterprise — contact [enterprise@http4k.org](mailto:enterprise@http4k.org) (if `reverseProxy()` is present in your v4.x line) |\n\nThe fix changes the default matcher to `Exact`. Existing callers that genuinely need substring matching (e.g. AWS subdomain dispatch) must explicitly pass `matcher = Contains`.\n\n### Workarounds\n\nFor deployments that cannot upgrade immediately: wrap your `reverseProxy()` with a host-allow-list filter that requires an exact match against expected vhost names before delegating.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.http4k:http4k-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "6.0.0.0"
      }, {
        "fixed" : "6.49.0.0"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.http4k:http4k-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "5.0.0.0"
      }, {
        "fixed" : "5.42.0.0"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.http4k:http4k-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.51.0.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/http4k/http4k/security/advisories/GHSA-jrpc-7vxp-69p6"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/http4k/http4k/commit/0121b05537"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/http4k/http4k/commit/54c6385615"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/http4k/http4k"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/http4k/http4k/releases/tag/6.49.0.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-444" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-19T21:15:59Z",
    "nvd_published_at" : null
  }
}