Yes. com.liferay:com.liferay.site.browser.web (Maven): upgrade to 6.0.5 or later; com.liferay.portal:com.liferay.portal.impl (Maven): upgrade to 7.7.9 or later; com.liferay.portal:release.dxp.bom (Maven): upgrade to 7.2.10.fp13 or later; com.liferay.portal:release.portal.bom (Maven): upgrade to 7.4.2-ga3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-26595?
Check whether you run com.liferay:com.liferay.site.browser.web (Maven), com.liferay.portal:com.liferay.portal.impl (Maven), com.liferay.portal:release.dxp.bom (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.liferay:com.liferay.site.browser.web (Maven): upgrade to 6.0.5 or later
# set com.liferay:com.liferay.site.browser.web to 6.0.5 in your pom.xml or build.gradle
com.liferay.portal:com.liferay.portal.impl (Maven): upgrade to 7.7.9 or later
# set com.liferay.portal:com.liferay.portal.impl to 7.7.9 in your pom.xml or build.gradle
com.liferay.portal:release.dxp.bom (Maven): upgrade to 7.2.10.fp13 or later
# set com.liferay.portal:release.dxp.bom to 7.2.10.fp13 in your pom.xml or build.gradle
com.liferay.portal:release.portal.bom (Maven): upgrade to 7.4.2-ga3 or later
# set com.liferay.portal:release.portal.bom to 7.4.2-ga3 in your pom.xml or build.gradle