Yes. org.jenkins-ci.plugins:git (Maven): upgrade to 4.11.2 or later; org.jenkins-ci.plugins:mercurial (Maven): upgrade to 2.16.1 or later; org.jenkins-ci.plugins:repo (Maven): upgrade to 1.14.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-30949?
Check whether you run org.jenkins-ci.plugins:git (Maven), org.jenkins-ci.plugins:mercurial (Maven) or org.jenkins-ci.plugins:repo (Maven) 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.jenkins-ci.plugins:git (Maven): upgrade to 4.11.2 or later
# set org.jenkins-ci.plugins:git to 4.11.2 in your pom.xml or build.gradle
org.jenkins-ci.plugins:mercurial (Maven): upgrade to 2.16.1 or later
# set org.jenkins-ci.plugins:mercurial to 2.16.1 in your pom.xml or build.gradle
org.jenkins-ci.plugins:repo (Maven): upgrade to 1.14.1 or later
# set org.jenkins-ci.plugins:repo to 1.14.1 in your pom.xml or build.gradle