Security Vulnerability - Java4Shell (CVE-2026-114938)

Modified on Thu, 19 Nov at 9:50 PM

November 19, 2026

Glo 2.0 and the customer data it stores and processes are not affected by CVE-2026-114938. No customer action is required.

 

At a glance

AreaStatus
Glo 2.0 application services 
Not affected
Customer data
No indicators of compromise
Internal infrastructure
Two non-internet-facing components in remediation
Exploitation in the wild 
None reported
Customer action required 
None

About the vulnerability

CVE-2026-114938 is a heap memory-corruption flaw in the Java HotSpot compiler's Base64 decoder. A crafted input can make the decoder write past its output buffer. A system is exposed only when all three conditions apply:

  1. It runs OpenJDK 17.0.6 or newer (branches 17, 21, 25 or 27), or a distribution built from it, without the vendor fix.

  2. It runs on x86-64 processors with AVX-512 VBMI (Intel Ice Lake or newer, AMD Zen 4 or newer). ARM processors are not affected.

  3. It decodes Base64 from external input, such as authentication headers or tokens.

Public proofs of concept exist. No successful exploitation has been reported.

 

Our response

Globality assessed every Java workload in its production (US and EU) and test environments on November 19, 2026.

  • Glo 2.0 is not affected. Its application services run a patched Java runtime on ARM-based AWS Graviton compute, so they meet neither the version nor the hardware condition.

  • Two internal infrastructure components are in remediation. A CI/CD deployment service and an internal data integration service run an affected runtime. Neither is exposed to the public internet, and both decode Base64 only from authenticated, Globality-controlled or vendor-controlled sources.

  • Remediation timeline. Both components will be restricted to ARM compute by November 24, 2026, and upgraded to fixed Java runtimes by December 3, 2026.

  • Monitoring. Production infrastructure has centralized logging and 24x7 security monitoring, including alerting on JVM crashes and abnormal container restarts. Our review found no anomalies or related incidents as of November 19, 2026.

This response follows the vulnerability management controls in our SOC 2 Type 2 and ISO 27001:2022 programs.


What you need to do

No action is required from Glo customers. We will confirm in writing, on request, when remediation is complete.


Questions: Globality Information Security team, infosec@globality.com

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article