No. Junglewise Threat Intelligence has no report of CVE-2021-42697 being exploited in the wild.
How severe is CVE-2021-42697?
Low severity, with a CVSS score of 3.1, published 24 May 2022.
Which products and versions are affected?
com.typesafe.akka:aakka-http-core_2.13.0-M3 (Maven) ECOSYSTEM:introduced=10.1.0; com.typesafe.akka:akka-http-core_2.11 (Maven) ECOSYSTEM:introduced=10.1.0,fixed=10.1.15; com.typesafe.akka:akka-http-core_2.12 (Maven) ECOSYSTEM:introduced=10.1.0,fixed=10.1.15; com.typesafe.akka:akka-http-core_2.13 (Maven) ECOSYSTEM:introduced=10.1.0,fixed=10.1.15; and 3 more.
Is there a fix for CVE-2021-42697?
Yes. com.typesafe.akka:akka-http-core_2.11 (Maven): upgrade to 10.1.15 or later; com.typesafe.akka:akka-http-core_2.12 (Maven): upgrade to 10.1.15 or later; com.typesafe.akka:akka-http-core_2.13 (Maven): upgrade to 10.1.15 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2021-42697?
Check whether you run com.typesafe.akka:aakka-http-core_2.13.0-M3 (Maven), com.typesafe.akka:akka-http-core_2.11 (Maven), com.typesafe.akka:akka-http-core_2.12 (Maven) or one of the others listed 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
com.typesafe.akka:akka-http-core_2.11 (Maven): upgrade to 10.1.15 or later
# set com.typesafe.akka:akka-http-core_2.11 to 10.1.15 in your pom.xml or build.gradle
com.typesafe.akka:akka-http-core_2.12 (Maven): upgrade to 10.1.15 or later
# set com.typesafe.akka:akka-http-core_2.12 to 10.1.15 in your pom.xml or build.gradle
com.typesafe.akka:akka-http-core_2.13 (Maven): upgrade to 10.1.15 or later
# set com.typesafe.akka:akka-http-core_2.13 to 10.1.15 in your pom.xml or build.gradle