# CVE-2026-54148: http4k: `DigestAuthProvider.verify` did not bind to request URI

> Attackers can replay captured Digest authentication responses against different URLs to bypass security controls and gain unauthorized access.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-p28p-j94q-pg32

## What is CVE-2026-54148?

CVE-2026-54148 is a high-severity authentication bypass vulnerability in http4k, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

http4k is a functional toolkit for Kotlin HTTP applications. Prior to 4.51.0.0, 5.42.0.0, and 6.50.0.0, DigestAuthProvider.verify in http4k-security-digest does not compare the uri parameter in an Authorization: Digest response with the actual request URL. An attacker who captures a valid Digest authentication response can replay it against another URL served by the same realm, bypassing the per-request-URI binding and potentially gaining unauthorized read or write access. This issue is fixed in versions 4.51.0.0, 5.42.0.0, and 6.50.0.0.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

## Which versions are affected by CVE-2026-54148?

6 open source packages ship an affected version, including org.http4k:http4k-security-digest.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.http4k:http4k-security-digest` | Maven | From 4.0.0.0 | 4.51.0.0 |
| `org.http4k:http4k-security-digest` | Maven | From 4.0.0.0 | 4.51.0.0 |
| `org.http4k:http4k-security-digest` | Maven | From 5.0.0.0 | 5.42.0.0 |
| `org.http4k:http4k-security-digest` | Maven | From 5.0.0.0 | 5.42.0.0 |
| `org.http4k:http4k-security-digest` | Maven | From 6.0.0.0 | 6.50.0.0 |
| `org.http4k:http4k-security-digest` | Maven | From 6.0.0.0 | 6.50.0.0 |

## How do I fix CVE-2026-54148?

Upgrade org.http4k:http4k-security-digest to a fixed version for your release line: 4.51.0.0, 5.42.0.0 or 6.50.0.0.

## Is CVE-2026-54148 being exploited?

There is no known exploitation of CVE-2026-54148 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54148 and fix it if it is affected.

What it is: CVE-2026-54148 is a high-severity authentication bypass vulnerability in http4k, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-54148 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.http4k:http4k-security-digest (Maven): affected from 4.0.0.0; fixed in 4.51.0.0
- org.http4k:http4k-security-digest (Maven): affected from 4.0.0.0; fixed in 4.51.0.0
- org.http4k:http4k-security-digest (Maven): affected from 5.0.0.0; fixed in 5.42.0.0
- org.http4k:http4k-security-digest (Maven): affected from 5.0.0.0; fixed in 5.42.0.0
- org.http4k:http4k-security-digest (Maven): affected from 6.0.0.0; fixed in 6.50.0.0
- org.http4k:http4k-security-digest (Maven): affected from 6.0.0.0; fixed in 6.50.0.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54148/ (Markdown: https://insights.sbomify.com/CVE-2026-54148/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54148
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54148
- OSV: https://osv.dev/vulnerability/CVE-2026-54148

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54148/
Summaries are generated and may contain mistakes; the official description above is the record.