github cardano-foundation/cardano-rosetta-java 1.5.5

latest release: 2.4.2
40 minutes ago

Cardano Rosetta Java v1.5.5

Cardano Rosetta Java v1.5.5 is a security release for the legacy 1.x line. 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 1.x 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, v1.5.5 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 1.x release will move to the fixed JDK.

Key Improvements

  • The API, indexer and all-in-one images set JDK_JAVA_OPTIONS=-XX:-UseBASE64Intrinsics, so every deployment of these images gets the workaround: Docker Compose, the all-in-one image, 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.
  • The 1.x line no longer tags its API and indexer images as latest on Docker Hub. latest belongs to the 2.x line.

Upgrade / Compatibility

  • From v1.4.x or v1.5.x: Compatible, no resync required. Preserve the existing indexer database and Cardano Node data, and redeploy with the v1.5.5 images. The JDK (Eclipse Temurin 25.0.5+8), Yaci Store, Cardano Node (11.1.3) and Mithril are unchanged, so the database schema does not change.
  • 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 indexer containers (or on the all-in-one container) 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.
  • Docker latest tags: The cardano-rosetta-java-api:latest and cardano-rosetta-java-indexer:latest tags no longer point to 1.x images. Pin an explicit version tag (1.5.5) for 1.x deployments. The all-in-one image cardano-rosetta-java:latest is still published by this line.
  • Already on v2.x: Stay on the 2.x line and upgrade to v2.4.2, which has the same workaround. This release is not a downgrade path.

API / Configuration

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

Environment updates:

  • API_DOCKER_IMAGE_TAG: 1.5.4 → 1.5.5 for Mainnet and Preprod Docker Compose.
  • INDEXER_DOCKER_IMAGE_TAG: 1.5.4 → 1.5.5 for Mainnet and Preprod Docker Compose.
  • JDK_JAVA_OPTIONS: now -XX:-UseBASE64Intrinsics by default in the images. No .env change is needed.

What's Changed

  • fix: Base64Utils and JDK_JAVA_OPTIONS baked into images for reported CVE-2026-114938 [1.5.x backport] by @matiwinnetou in #900
  • ci: stop the 1.5.x line from pushing :latest for the api and indexer images (2ff61e1)
  • chore: prepare version 1.5.5 (f40a480)

Full Changelog: 1.5.4...1.5.5

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

NewReleases is sending notifications on new releases.