Action required: mitigation for the Java vulnerability (CVE-2026-114938)
On November 18, 2026, a vulnerability in the Base64 decoding of OpenJDK (Java) was disclosed (CVE-2026-114938). On CPUs with certain features, decoding crafted data may corrupt memory and allow arbitrary code to be executed.
In the Marketplace edition of AGENTIC STAR, the sign-in platform (Keycloak) and the conversation search platform (OpenSearch) run on affected versions of Java. We will announce a version that includes a fixed Java here as soon as it is ready. Until then, please apply a temporary mitigation by following the steps below.
Scope
| Item | Details |
|---|---|
| Affected Java versions | 17.0.6 to 17.0.21, 21 to 21.0.13, 25 to 25.0.5, 27 to 27.0.1 |
| Affected CPUs | x86-64 CPUs that have all of avx512f, avx512bw, avx512vbmi, and bmi2 (Intel Ice Lake or later, AMD Zen 4 or later) |
| Products that require your action | Marketplace edition (Agenticstar ADK Advanced and Basic). All versions including v3.4.0, all clouds |
| Products that do not require your action | SaaS edition (we handle it) |
Even with the same VM size, the CPU can differ depending on the host the VM is placed on. Apply the mitigation even if the CPUs of your current nodes do not match the conditions.
Mitigation
Add -XX:-UseBASE64Intrinsics to the Java options. Java then stops using the vulnerable code path.
Expected downtime
Changing the settings recreates the Pods one at a time. Apply the mitigation when usage is low.
| Target | Downtime |
|---|---|
| Sign-in platform | With 1 replica (the default), users cannot sign in for about 2 minutes. With 3 replicas, there is no downtime |
| Conversation search platform | No downtime. Recreating the Pods takes several minutes (longer with more data) |
Steps
1. Connect to the cluster
Connect kubectl to the cluster in the same way as during deployment.
- Azure: "Verifying the Deployment" in the quickstart
- AWS: "Configure kubectl" under "After Deployment" in the quickstart
2. Apply to the sign-in platform
kubectl set env statefulset/keycloak-extensions-keycloakx -n librechat-auth \
-c keycloak JDK_JAVA_OPTIONS=-XX:-UseBASE64Intrinsics
kubectl rollout status statefulset/keycloak-extensions-keycloakx \
-n librechat-auth --timeout=15m
3. Apply to the conversation search platform
kubectl set env statefulset/chat-opensearch-master statefulset/chat-opensearch-data \
-n agentic-star-front -c opensearch JDK_JAVA_OPTIONS=-XX:-UseBASE64Intrinsics
kubectl rollout status statefulset/chat-opensearch-master \
-n agentic-star-front --timeout=30m
kubectl rollout status statefulset/chat-opensearch-data \
-n agentic-star-front --timeout=30m
4. Verify
Check that the option is in effect for Java in each Pod.
for p in $(kubectl get pod -n librechat-auth -o name | grep keycloak-extensions-keycloakx-); do
echo "$p: $(kubectl exec -n librechat-auth "$p" -c keycloak -- \
jcmd 0 VM.flags 2>/dev/null | grep -c -- -XX:-UseBASE64Intrinsics)"
done
for p in $(kubectl get pod -n agentic-star-front -o name | grep chat-opensearch-); do
echo "$p: $(kubectl exec -n agentic-star-front "$p" -c opensearch -- \
jcmd 0 VM.flags 2>/dev/null | grep -c -- -XX:-UseBASE64Intrinsics)"
done
If 1 is shown for each Pod of the sign-in platform and 2 for each Pod of the conversation search platform, the option is in effect for all Java processes (two Java processes run in each Pod of the conversation search platform).
Also check that the status of the conversation search platform is back to green.
kubectl exec -n agentic-star-front chat-opensearch-master-0 -c opensearch -- \
curl -s 'localhost:9200/_cluster/health?pretty' | grep '"status"'
Product upgrades
- After upgrading the product, verify again with step 4. If the option is not in effect, run steps 2 and 3 again.
- v3.4.0 also runs on affected versions of Java. Apply the mitigation by following these steps in environments newly deployed with v3.4.0 as well.
- We will announce here when a version that includes a fixed Java is available. After upgrading to that version, you can remove the mitigation.
Revert
Reverting also recreates the Pods, so the downtime is the same as when applying.
kubectl set env statefulset/keycloak-extensions-keycloakx -n librechat-auth \
-c keycloak JDK_JAVA_OPTIONS-
kubectl set env statefulset/chat-opensearch-master statefulset/chat-opensearch-data \
-n agentic-star-front -c opensearch JDK_JAVA_OPTIONS-