Repository navigation
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
apiandyaci-indexerimages setJDK_JAVA_OPTIONS=-XX:-UseBASE64Intrinsics, so every deployment of these images gets the workaround: Docker Compose, the Helm chart, and your own Kubernetes ordocker runsetups. The JVM logsNOTE: Picked up JDK_JAVA_OPTIONS: -XX:-UseBASE64Intrinsicson 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 setJDK_JAVA_OPTIONSyourself, it replaces the image default. Keep-XX:-UseBASE64Intrinsicsin it. - Not ready to upgrade? Set
JDK_JAVA_OPTIONS=-XX:-UseBASE64Intrinsicson theapiandyaci-indexercontainers 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=trueandTOKEN_REGISTRY_LOGO_FETCH=true. The workaround covers every otherjava.util.Base64use in the JVM as well.
API / Configuration
/network/options: reported middleware version updated.version.middleware_versionis now2.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:-UseBASE64Intrinsicsby default in the images. No.envor Helm change is needed.
What's Changed
- ci: split release testing into independently triggerable steps by @linconvidal in #837
- test: assert zero-value withdrawals are omitted from operations by @linconvidal in #838
- fix: repair Preprod dispatch checkout and Compose image preparation by @linconvidal in #839
- fix: Base64Utils and JDK_JAVA_OPTIONS baked into images for reported CVE-2026-114938 by @matiwinnetou in #899
- chore: prepare version 2.4.2 (da999d0)
Full Changelog: 2.4.1...2.4.2