github cardano-foundation/cardano-rosetta-java 2.4.2

32 minutes ago

Cardano Rosetta Java v2.4.2

Cardano Rosetta Java v2.4.2 is a security release. It mitigates CVE-2026-114938 ("Java4Shell") in the JDK's Base64 decoder until a fixed JDK is available.

Caution

This is a mandatory release. All operators should upgrade. CVE-2026-114938 is a memory corruption flaw in the hardware-accelerated java.util.Base64 decoder of OpenJDK 17 and later. It can allow remote code execution on x64 CPUs that support AVX-512 VBMI. The fixed Eclipse Temurin build (25.0.5.1+2) has been announced by Adoptium but is not published yet. Until it is, v2.4.2 applies the workaround Adoptium recommends: the JVM option -XX:-UseBASE64Intrinsics, which makes Base64 decoding run as plain Java instead of the affected intrinsic. A later release will move to the fixed JDK.

Key Improvements

  • The api and yaci-indexer images set JDK_JAVA_OPTIONS=-XX:-UseBASE64Intrinsics, so every deployment of these images gets the workaround: Docker Compose, the Helm chart, and your own Kubernetes or docker run setups. The JVM logs NOTE: Picked up JDK_JAVA_OPTIONS: -XX:-UseBASE64Intrinsics on startup.
  • Base64 decoding of CIP-26 token registry logos moved into a small shared helper. The output is unchanged.

Upgrade / Compatibility

  • From v2.x: Compatible, no resync required. Preserve the existing indexer database and Cardano Node data, and redeploy with the v2.4.2 images. The JDK (Eclipse Temurin 25.0.5+8), Yaci Store, Cardano Node and Mithril are unchanged.
  • From v1.x: Requires a full yaci-indexer resync only (Cardano Node data can be kept). See the resync procedure. Operators staying on 1.x must upgrade to v1.5.5, which has the same workaround.
  • Your own JDK_JAVA_OPTIONS: If you set JDK_JAVA_OPTIONS yourself, it replaces the image default. Keep -XX:-UseBASE64Intrinsics in it.
  • Not ready to upgrade? Set JDK_JAVA_OPTIONS=-XX:-UseBASE64Intrinsics on the api and yaci-indexer containers of your current release and restart.
  • Exposure in Rosetta: No Rosetta API endpoint base64-decodes request input. The only decode path is CIP-26 logos from the token registry, which runs only with TOKEN_REGISTRY_ENABLED=true and TOKEN_REGISTRY_LOGO_FETCH=true. The workaround covers every other java.util.Base64 use in the JVM as well.

API / Configuration

  • /network/options: reported middleware version updated.
    • version.middleware_version is now 2.4.2. Request and response schemas, operation types and error codes are unchanged.

Environment updates:

  • RELEASE_VERSION: 2.4.1 → 2.4.2.
  • Helm global.releaseVersion: "2.4.1" → "2.4.2".
  • JDK_JAVA_OPTIONS: now -XX:-UseBASE64Intrinsics by default in the images. No .env or Helm change is needed.

What's Changed

Full Changelog: 2.4.1...2.4.2

Don't miss a new cardano-rosetta-java release

NewReleases is sending notifications on new releases.