Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-54147 medium CVSS 6.5

Vulnerability in org.http4k:http4k-security-digest (CVE-2026-54147)

Summary

Vulnerability in org.http4k:http4k-security-digest (CVE-2026-54147). Data can be tampered with by attackers. Exploitable via DigestAuthProvider.verify. Mitigation: upgrade to 6.50.0.0 or later.

Original description

The description as published by the source.

Impact

An issue in DigestAuthProvider.verify:

Algorithm silently forced to MD5. The configured algorithm parameter was ignored — every verification used MD5 regardless of configuration. Deployments believing they were running SHA-256 Digest auth were silently inheriting MD5's collision weaknesses, including documented attack paths against Digest schemes that rely on the hash being collision-resistant.

Who is affected: any application using http4k-security-digest for HTTP Digest authentication. The bug has been present since DigestAuthProvider was introduced (commit 8a52b615b1, 2021).

Patches

Line Fixed in Edition
v6.x (Community) 6.50.0.0 Community
v5.x (LTS) 5.42.0.0 Enterprise — contact enterprise@http4k.org (if Digest auth is present in your v5.x line)
v4.x (LTS) 4.51.0.0 Enterprise — contact enterprise@http4k.org (if Digest auth is present in your v4.x line)

The fix:

  • Hashes with the configured algorithm instead of hardcoded MD5.

Workarounds

For deployments that cannot upgrade immediately:

  • Algorithm gap: do not rely on algorithm configuration; assume MD5 is in use and treat the Digest credentials as low-trust.

References

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-54147 has been found in org.http4k:http4k-security-digest.
Attackers can target a specific entry point like DigestAuthProvider.verify over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade org.http4k:http4k-security-digest to 6.50.0.0 or later.
If unsure, ask your IT team or search "org.http4k:http4k-security-digest CVE-2026-54147" on the vendor's site.

CVE-2026-54147 (org.http4k:http4k-security-digest) — CWE-327 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: DigestAuthProvider.verify / algorithm / DigestAuthProvider
Patched: 6.50.0.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-327) exists in org.http4k:http4k-security-digest. Attackers reach the vulnerable code path via DigestAuthProvider.verify without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of org.http4k:http4k-security-digest. Attack surface: DigestAuthProvider.verify / algorithm / DigestAuthProvider.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 6.50.0.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.http4k:http4k-security-digest を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.http4k:http4k-security-digest to 6.50.0.0

    ステージング環境で 6.50.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.http4k:http4k-security-digest
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"4.48.2.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details