Security Advisories
This page lists publicly disclosed vulnerabilities that our customers have asked about, whether they affect ActivityInfo SaaS or the ActivityInfo Self-Managed Server, and what we have done about them. For our overall approach to security, see ISO-27001 & Data Security.
Java4Shell (CVE-2026-114938)
Published November 18, 2026
On November 17, 2026, researchers working with OpenAI disclosed a memory-corruption bug in Java's Base64 decoder, which they called "Java4Shell". The bug only occurs on x86-64 processors that support AVX-512 VBMI: Intel Ice Lake and later, and AMD Zen 4 and later.
ActivityInfo SaaS: We disabled the vulnerable component on all ActivityInfo SaaS servers using the -XX:-UseBASE64Intrinsics flag. The change was fully in place at 07:54 UTC on November 18, 2026. We found no evidence of exploitation. No action is needed from customers.
ActivityInfo Self-Managed Server: Versions 5.0.0, 5.0.1, 5.1.0, 5.1.1 and 5.2.0 include an affected version of Java; versions 4.x do not. We reviewed every place in the code where the self-managed server decodes Base64 data and concluded that this vulnerability is not exploitable in any self-managed version. Nonetheless, out of an abundance of caution, versions 5.1.2 and 5.2.1 disable the vulnerable component using the same flag. If you run 5.0.x, 5.1.x or 5.2.0, we recommend upgrading to 5.1.2 or 5.2.1.
The flag has no functional effect and imposes no measurable performance cost on ActivityInfo.
PHP2Shell (CVE-2026-109618, CVE-2026-109619)
Published November 18, 2026
In October 2026, two critical vulnerabilities in PHP were disclosed that allow remote code execution on servers running PHP.
Not affected. ActivityInfo SaaS, the ActivityInfo Self-Managed Server, our website and our internal systems do not use PHP.