Skip to main content
Question

Log4J vulnerability CVE-2025-68161 on Prem A360 v38

  • March 19, 2026
  • 0 replies
  • 3 views

Hi all, 

Security team in my company flagged our Automation Anywhere instance as potential vulnerability due to the obsolete version of Log4j-core.jar file. I tried searching for the answers in here and within release notes but the only information I found was regarding the vulnerabilities CVE-2025-xxx with version up to 2.17. This issue is regarding the CVE-2025-68161 and it refers to Apache Log4j 2.0-beta9 < 2.25.3 MitM. 

As per Apache Log4j 2.0-beta9 < 2.25.3 MitM | Tenable®

As far as I could check online there is no subject on forum about releasing a newer version. Do you know if the fix is planned for it in incoming version? And if not is there any way that I would be able to replace the current library with newer one or “install” it separately to A360?

We are currently running v39 on Prem with Build 42436.

If you would need more details please let me know.