Skip to content

fix(opensearch): Pass the Base64 intrinsics mitigation via jvm.options.d - #1745

Merged
dervoeti merged 2 commits into
mainfrom
fix/opensearch-base64-intrinsics-cve-2026-114938
Nov 18, 2026
Merged

dervoeti merged 2 commits into
mainfrom
fix/opensearch-base64-intrinsics-cve-2026-114938

Conversation

@dervoeti

@dervoeti dervoeti commented Nov 18, 2026 •

Copy link
Copy Markdown
Member

Description

Follow-up to #1741.

OpenSearch ignores JAVA_TOOL_OPTIONS, bin/opensearch-env prints warning: ignoring JAVA_TOOL_OPTIONS=... and unsets it before starting the JVM.

Snippet from bin/opensearch-env:

# do not let JAVA_TOOL_OPTIONS slip in (as the JVM does by default)
if [ ! -z "$JAVA_TOOL_OPTIONS" ]; then
  echo "warning: ignoring JAVA_TOOL_OPTIONS=$JAVA_TOOL_OPTIONS"
  unset JAVA_TOOL_OPTIONS
fi

So the CVE-2026-114938 mitigation from jdk-base has no effect on OpenSearch, the Base64 intrinsics stay enabled.
The other Java based images don't seem to behave similarly, only OpenSearch needs this special treatment.

The fix is to write -XX:-UseBASE64Intrinsics to config/jvm.options.d/cve-2026-114938.options, which OpenSearch reads on startup. OpenSearch still logs the ignoring JAVA_TOOL_OPTIONS warning on startup, because jdk-base sets the variable. This is expected.

I built opensearch 3.6.0 locally for amd64 to test it, looked good.

Definition of Done Checklist

Note

Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant.

Please make sure all these things are done and tick the boxes

  • Changes are OpenShift compatible
  • All added packages (via microdnf or otherwise) have a comment on why they are added
  • Things not downloaded from Red Hat repositories should be mirrored in the Stackable repository and downloaded from there
  • All packages should have (if available) signatures/hashes verified
  • Add an entry to the CHANGELOG.md file
  • Integration tests ran successfully
TIP: Running integration tests with a new product image

The image can be built and uploaded to the kind cluster with the following commands:

boil build <IMAGE> --image-version <RELEASE_VERSION> --strip-architecture --load
kind load docker-image <MANIFEST_URI> --name=<name-of-your-test-cluster>

See the output of boil to retrieve the image manifest URI for <MANIFEST_URI>.

@dervoeti
dervoeti force-pushed the fix/opensearch-base64-intrinsics-cve-2026-114938 branch from b978c7b to 077f76d Compare November 18, 2026 14:41
@dervoeti dervoeti moved this to Development: Waiting for Review in Stackable Engineering Nov 18, 2026
@dervoeti
dervoeti added this pull request to the merge queue Nov 18, 2026
Merged via the queue into main with commit 0b0a7b0 Nov 18, 2026
3 checks passed
@dervoeti
dervoeti deleted the fix/opensearch-base64-intrinsics-cve-2026-114938 branch November 18, 2026 15:17
@sbernauer sbernauer moved this from Development: Waiting for Review to Development: Done in Stackable Engineering Nov 18, 2026
@lfrancke lfrancke moved this from Development: Done to Done in Stackable Engineering Nov 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Development

Successfully merging this pull request may close these issues.

4 participants