CVE-2026-120317: http4k Digest authentication missing body integrity in auth-int

CVE-2026-120317 · Severity: medium · CVSS 5.9 · Published 2026-11-02

http4k is a Kotlin HTTP toolkit used to build APIs and microservices. The vulnerability allows attackers on unencrypted networks to modify the body of authenticated requests (such as changing a payment amount or account number) while the authentication header remains valid. This bypasses the auth-int integrity protection that administrators may have enabled to protect requests without TLS encryption.

Technologies: Http4k-Security-Digest. Vendors: Http4k.

Quick answers

Is CVE-2026-120317 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-120317 being exploited in the wild.
How severe is CVE-2026-120317?
Medium severity, with a CVSS score of 5.9, published 2 November 2026.
Which products and versions are affected?
Http4k-Security-Digest 4.9.10.0 through 6.59.0.0.
Is there a fix for CVE-2026-120317?
Yes: fixed in 6.60.0.0. Until then: Avoid using auth-int QoP on non-TLS channels; use TLS encryption (HTTPS) instead to provide transport-level integrity, or use a stronger authentication mechanism instead of Digest authentication. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-120317 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-120317?
Check whether you run Http4k-Security-Digest at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 6.60.0.0

Avoid using auth-int QoP on non-TLS channels; use TLS encryption (HTTPS) instead to provide transport-level integrity, or use a stronger authentication mechanism instead of Digest authentication.

Technical details

The DigestEncoder fails to include the request entity body in the auth-int QoP digest calculation, computing only H(method:digestUri) instead of the RFC 7616-compliant H(method:digestUri:H(entity-body)). An on-path attacker can tamper with the request body on non-TLS channels while the Authorization header remains valid, as the server-side DigestAuthProvider.verify() method has no body parameter and cannot detect the tampering. Exploitation requires non-default QoP configuration (auth-int), a non-TLS channel, and an active MITM position.

Affected products

  • http4k http4k-security-digest 4.9.10.0 through 6.59.0.0

Timeline

  • 2026-10-16: disclosed
  • 2026-11-02: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.