No. Junglewise Threat Intelligence has no report of CVE-2022-21653 being exploited in the wild.
How severe is CVE-2022-21653?
Low severity, with a CVSS score of 3.1, published 6 January 2022.
Which products and versions are affected?
org.typelevel:jawn-parser_0.25 (Maven) ECOSYSTEM:introduced=0; org.typelevel:jawn-parser_0.27 (Maven) ECOSYSTEM:introduced=0; org.typelevel:jawn-parser_2.10 (Maven) ECOSYSTEM:introduced=0; org.typelevel:jawn-parser_2.11 (Maven) ECOSYSTEM:introduced=0; and 14 more.
Is there a fix for CVE-2022-21653?
Yes. org.typelevel:jawn-parser_2.12 (Maven): upgrade to 1.3.2 or later; org.typelevel:jawn-parser_2.13 (Maven): upgrade to 1.3.2 or later; org.typelevel:jawn-parser_3 (Maven): upgrade to 1.3.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-21653?
Check whether you run org.typelevel:jawn-parser_0.25 (Maven), org.typelevel:jawn-parser_0.27 (Maven), org.typelevel:jawn-parser_2.10 (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
org.typelevel:jawn-parser_2.12 (Maven): upgrade to 1.3.2 or later
# set org.typelevel:jawn-parser_2.12 to 1.3.2 in your pom.xml or build.gradle
org.typelevel:jawn-parser_2.13 (Maven): upgrade to 1.3.2 or later
# set org.typelevel:jawn-parser_2.13 to 1.3.2 in your pom.xml or build.gradle
org.typelevel:jawn-parser_3 (Maven): upgrade to 1.3.2 or later
# set org.typelevel:jawn-parser_3 to 1.3.2 in your pom.xml or build.gradle