No. Junglewise Threat Intelligence has no report of CVE-2018-10237 being exploited in the wild.
How severe is CVE-2018-10237?
Low severity, with a CVSS score of 3.1, published 15 June 2020.
Which products and versions are affected?
com.google.guava:guava (Maven) ECOSYSTEM:introduced=11.0,fixed=24.1.1-android; com.google.guava:guava-jdk5 (Maven) ECOSYSTEM:introduced=0,last_affected=17.0; com.googlecode.guava-osgi:guava-osgi (Maven) ECOSYSTEM:introduced=0,last_affected=11.0.1; de.mhus.ports:vaadin-shared-deps (Maven) ECOSYSTEM:introduced=0,last_affected=7.4.0; and 1 more.
Is there a fix for CVE-2018-10237?
Yes. com.google.guava:guava (Maven): upgrade to 24.1.1-android or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2018-10237?
Check whether you run com.google.guava:guava (Maven), com.google.guava:guava-jdk5 (Maven), com.googlecode.guava-osgi:guava-osgi (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.google.guava:guava (Maven): upgrade to 24.1.1-android or later
# set com.google.guava:guava to 24.1.1-android in your pom.xml or build.gradle