Advisories
This weekExploitable · Confirmed

org.http4s:http4s-ember-core_2.12, org.http4s:http4s-ember-core_2.13: Http4s vulnerable to HTTP Request Smuggling due to improper handling…

There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.

Does it affect what I run?

Checked in your browser. The version you type is not sent anywhere.

Who is affected

  • org.http4s:http4s-ember-core_2.12 (Maven): every version, before 0.23.31
  • org.http4s:http4s-ember-core_2.13 (Maven): every version, before 0.23.31
  • org.http4s:http4s-ember-core_3 (Maven): every version, before 0.23.31
  • org.http4s:http4s-ember-core_2.13 (Maven): from 1.0.0-M1, before 1.0.0-M45
  • org.http4s:http4s-ember-core_3 (Maven): from 1.0.0-M1, before 1.0.0-M45

The fix

  • org.http4s:http4s-ember-core_2.12 (Maven) fixed in 0.23.31

    maven
    mvn versions:use-dep-version -Dincludes=org.http4s:http4s-ember-core_2.12 -DdepVersion=0.23.31 -DforceVersion=true
    Check what is installed
    mvn dependency:tree -Dincludes=org.http4s:http4s-ember-core_2.12
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Maven dependency org.http4s:http4s-ember-core_2.12 to 0.23.31 or the nearest later release, to fix CVE-2025-59822. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • org.http4s:http4s-ember-core_2.13 (Maven) fixed in 0.23.31

    maven
    mvn versions:use-dep-version -Dincludes=org.http4s:http4s-ember-core_2.13 -DdepVersion=0.23.31 -DforceVersion=true
    Check what is installed
    mvn dependency:tree -Dincludes=org.http4s:http4s-ember-core_2.13
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Maven dependency org.http4s:http4s-ember-core_2.13 to 0.23.31 or the nearest later release, to fix CVE-2025-59822. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • org.http4s:http4s-ember-core_2.13 (Maven) fixed in 1.0.0-M45

    maven
    mvn versions:use-dep-version -Dincludes=org.http4s:http4s-ember-core_2.13 -DdepVersion=1.0.0-M45 -DforceVersion=true
    Check what is installed
    mvn dependency:tree -Dincludes=org.http4s:http4s-ember-core_2.13
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Maven dependency org.http4s:http4s-ember-core_2.13 to 1.0.0-M45 or the nearest later release, to fix CVE-2025-59822. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • org.http4s:http4s-ember-core_3 (Maven) fixed in 0.23.31

    maven
    mvn versions:use-dep-version -Dincludes=org.http4s:http4s-ember-core_3 -DdepVersion=0.23.31 -DforceVersion=true
    Check what is installed
    mvn dependency:tree -Dincludes=org.http4s:http4s-ember-core_3
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Maven dependency org.http4s:http4s-ember-core_3 to 0.23.31 or the nearest later release, to fix CVE-2025-59822. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • org.http4s:http4s-ember-core_3 (Maven) fixed in 1.0.0-M45

    maven
    mvn versions:use-dep-version -Dincludes=org.http4s:http4s-ember-core_3 -DdepVersion=1.0.0-M45 -DforceVersion=true
    Check what is installed
    mvn dependency:tree -Dincludes=org.http4s:http4s-ember-core_3
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Maven dependency org.http4s:http4s-ember-core_3 to 1.0.0-M45 or the nearest later release, to fix CVE-2025-59822. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.

Fix commands generated from the advisory's versions. No model wrote them.

In plain words

Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.

Evidence

Timeline

  1. First published here, as "For your digest".
  2. Level changed from "For your digest" to "This week".
  3. Evidence added: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))