Treasure AI
Security Advisories
This page provides updates on critical security vulnerabilities and their potential impact on Treasure AI’s externally facing production services. Each advisory explains our current assessment, response actions, and any steps customers need to take. We’ll add new advisories and update existing ones as assessments and remediation progress, with a “last updated” date on each entry.
Security update: CVE-2026-114938
Java4Shell — OpenJDK Base64 decoder
Published: November 19, 2026, 00:00 UTC (November 18, 7:00 PM EST)
Scope: Internet-facing production systems operated by Treasure AI (TAI)
Status: Mitigated — permanent remediation pending
What happened?
On November 17, 2026, a critical vulnerability known as Java4Shell (CVE-2026-114938) was publicly disclosed. It affects certain unpatched OpenJDK builds in Java 17 and later release lines. The flaw is in the Java runtime’s Base64 decoder, which applications may use to process encoded data such as credentials and tokens.
On affected runtime and processor configurations, specially crafted input can corrupt application memory, causing a crash or service disruption. In some circumstances, an attacker could execute code without first authenticating. Exposure depends on the running Java build, processor capabilities and whether untrusted input reaches the vulnerable decoder.
Public reporting: As of November 18, 2026, there are no reports of exploitation in the wild. A public proof of concept is available, and Calif reports successful exploitation in research testing.
Oracle released security updates on November 17, 2026. Fixed-build availability and version numbers vary by Java distribution; deployment and validation are needed to confirm that an application is running a corrected runtime.
Official CVE: CVE-2026-114938
Vendor advisory: Oracle Critical Security Patch Update Advisory - November 2026
Is TAI impacted?
TAI has deployed mitigations across all affected Internet-facing production services. These measures address the vulnerable processing path and reduce exposure to CVE-2026-114938.
What TAI is doing
We have disabled the vulnerable Java processing path in the affected production configurations. We will deploy applicable security patches from our Java runtime providers, including additional fixes as they become available.
What customers need to do
We are confirming whether any customer action is needed for the services under review. We will provide specific instructions if action is required.
Further updates
We will post updates as needed. For questions, please contact Support and/or your Customer Success Manager (CSM).