Skip to main content
CVE-2026-120317VulnerabilityPublished

http4k from 4.9.10.0 before 6.60.0.0 contains a missing integrity check vulnerability because DigestEncoder computes

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-120317· High 8.2

Not known to be exploited · CVSS 8.2 High : upgrade to 6.60.0.0 soon.

Data as of 2 Nov 2026, 04:59 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.2
CNA (VulnCheck)CVSS 3.15.9
Patch
Available – fixed in 6.60.0.0
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

What to do

Upgrade http4k to 6.60.0.0.

Affected software

ProductAffectedFixed in
http4khttp4kAffected
  • >=4.9.10.0 <6.60.0.0
Fixed in
  • 6.60.0.0
Mavenhttp4kpkg:maven/http4kOther threatsAffected
  • >=4.9.10.0 <6.60.0.0
Fixed in
  • 6.60.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, avoid using http4k over non-TLS channels to prevent on-path attackers from exploiting this vulnerability.

Description

A vulnerability in http4k versions from 4.9.10.0 up to but not including 6.60.0.0 allows on-path attackers on non-TLS channels to modify the body of authenticated requests without invalidating the Authorization header. This occurs because the DigestEncoder component does not hash the request entity body when computing the auth-int digest, resulting in a missing integrity check.

References

Community reviews

Loading reviews…