Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2021-42697

HIGH

CVE-2021-42697 is a high-severity (CVSS 7.5) CWE-674 vulnerability in com.typesafe.akka:akka-http-core_2.13.0-RC3. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2021-42697 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Uncontrolled Recursion in Akka HTTP

Also known asGHSA-3hw2-h67c-wq66
Published
Nov 2, 2021
Updated
Jul 9, 2026
Affected
9 pkgs
Patched
5 / 9
Exploits
2 known

Real-World Exposure

9 pkgs affected
com.typesafe.akka:akka-http-core_2.13.0-RC3com.typesafe.akka:akka-http-core_2.13.0-RC2com.typesafe.akka:akka-http-core_2.13.0-M5com.typesafe.akka:aakka-http-core_2.13.0-M3com.typesafe.akka:akka-http-core_2.13com.typesafe.akka:akka-http-core_2.13com.typesafe.akka:akka-http-core_2.12com.typesafe.akka:akka-http-core_2.12+1 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Akka HTTP 10.1.x before 10.1.15 and 10.2.x before 10.2.7 can encounter stack exhaustion while parsing HTTP headers, which allows a remote attacker to conduct a Denial of Service attack by sending a User-Agent header with deeply nested comments.

Affected Packages

9 total 5 fixed
EcosystemPackageVulnerable rangeFix
Mavencom.typesafe.akka:akka-http-core_2.13.0-RC310.1.0No fix
Mavencom.typesafe.akka:akka-http-core_2.13.0-RC210.1.0No fix
Mavencom.typesafe.akka:akka-http-core_2.13.0-M510.1.0No fix
Mavencom.typesafe.akka:aakka-http-core_2.13.0-M310.1.0No fix
Mavencom.typesafe.akka:akka-http-core_2.1310.1.0&&< 10.1.1510.1.15
Mavencom.typesafe.akka:akka-http-core_2.1310.2.0-M1&&< 10.2.710.2.7
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-50892remotemultiple

Akka HTTP 10.1.14 - Denial of Service

by cxosmo · May 11, 2022

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.typesafe.akka:akka-http-core_2.13.0-RC3. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    No patched version of com.typesafe.akka:akka-http-core_2.13.0-RC3 has shipped for CVE-2021-42697 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2021-42697 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2021-42697. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Akka HTTP 10.1.x before 10.1.15 and 10.2.x before 10.2.7 can encounter stack exhaustion while parsing HTTP headers, which allows a remote attacker to conduct a Denial of Service attack by sending a User-Agent header with deeply nested comments.
O3 Security · Impact-Aware SCA

Is CVE-2021-42697 in your dependencies?

O3 detects CVE-2021-42697 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.