OLIVE Platform Version 1.3.1
Status: Hotfix — the current release.
Overview
OLIVE 1.3.1 is a hotfix on top of 1.3.0. It was triggered by two upstream advisories published in late October 2026: a high-severity remote code execution flaw in the Brotli decompression code bundled with Node.js (node2shell, CVE-2026-111497), and the compromise of eight eMudhra intermediate CA private keys. Neither is a defect in OLIVE — both sit in the base images OLIVE's services are built from, where no configuration or values change can reach them.
Every container image in the release has been rebuilt on patched base images, re-signed and re-pinned by digest. A 1.3.1 deployment is not exposed to either issue.
Two unrelated defects reported against 1.3.0 are fixed as well: the template uiConfig field reference named the wrong property, and a JSONata transform serialised a repeated object as [Circular Reference].
Unlike 1.2.0 → 1.3.0, this is a chart version bump. There is no export, no redeploy and no data migration — see Upgrade.
Security
Node.js Brotli decompression RCE — node2shell (CVE-2026-111497)
The Brotli decompression code bundled with Node.js mishandles attacker-controlled input. Node.js rates it high severity. The impact is a crash, disclosure of process memory, or execution of attacker-supplied code. Proof-of-concept code is public; no exploitation in the wild was reported at the time of the advisory.
Every Node.js line released before 21 October 2026 is affected. In the 24.x line the fix is in 24.22.1.
Untrusted Brotli data reaches the decompressor in three ways: a request body sent with Content-Encoding: br to a framework that decodes it, a fetch() response from a server the caller does not control, and direct use of the node:zlib Brotli functions.
What changed. The affected code sits in the Node.js runtime inside OLIVE's images, so no chart or configuration change could mitigate it. In 1.3.1 the runtime base image gcr.io/distroless/nodejs24-debian13:nonroot is re-pinned to the build carrying Node.js 24.22.1, the build stages move to node:24.22.1-slim and node:24.22.1-alpine3.24, and every service image was rebuilt, signed with cosign and pinned by digest. Nothing in values.yaml changes. Deploying 1.3.1 is the whole fix.
eMudhra intermediate CA key compromise
On 20 October 2026 the Mozilla and Google Chrome root programs confirmed that the private keys of eight eMudhra intermediate CA certificates can be derived from their public certificates. A key ceremony on 30 April 2025 generated them with too little randomness. The keys were never stolen — anyone can compute them.
Six are TLS intermediates chaining to emSign ECC Root CA - G3. Two are code-signing intermediates. Sectigo cross-signed copies exist under AAA Certificate Services. Anyone holding one of these keys can issue a certificate for any hostname, and a client that trusts the root will accept it. Chrome found no affected TLS certificate in Certificate Transparency before it blocked them. Browsers and operating systems blocked the intermediates between 17 and 20 October, and Linux distributions and language runtimes shipped updated CA bundles on 20 and 21 October.
Why it concerned OLIVE. Browsers receive revocation data automatically. A container does not. A service that validates TLS against a CA bundle baked into its image keeps trusting the compromised chain until that bundle is replaced. The exposure is an outbound TLS connection from an OLIVE service — an HTTP datapoint, an AI caller, an MCP server call — to a host presenting a certificate issued under one of those intermediates.
What changed. The rebuilt base images carry the updated Node.js 24.22.1 bundle.
Fixes
Template uiConfig: the property is control, not controlType
The generated OLIVE type documentation declared the form control property as controlType, while the template pilet reads control. A field written as documented was causing templates to not render correctly.
The type documentation now declares control, with the values text, password, textarea and select. Instantiating a template that uses microfrontends writes control as well, and the field reference and examples in the Connectivity Developer Handbook were corrected.
A uiConfig you already authored with controlType behaves exactly as before — the property is ignored. Change it to control to get the control you intended.
JSONata transform: a repeated object serialised as [Circular Reference]
When the result of a JSONata transform datapoint contained the same object in more than one place, 1.3.0 serialised the first occurrence and replaced every later one with the string [Circular Reference]. The object did not have to be circular — being referenced twice was enough. OLIVE 1.1 returned it correctly, so the defect typically surfaced while migrating connectivity from 1.1 to 1.3.
Result serialisation now treats a reference as circular only when it points back into the structure enclosing it, so an object used more than once is serialised at each position. A genuinely circular structure is still replaced with [Circular Reference] rather than failing the invocation.
Compatibility Matrix changes
The 1.3.0 compatibility matrix applies unchanged apart from the rows below. Kubernetes 1.31 or later is still the floor, and Traefik is still the only supported ingress controller.
| Component | 1.3.0 | 1.3.1 |
|---|---|---|
| Temporal server and admin-tools | 1.31.2 | 1.31.4 |
| Temporal UI (development only) | 2.53.3 | 2.57.0 |
| Node.js build-stage image (slim) | 24.21.0-slim | 24.22.1-slim |
| Node.js build-stage image (Alpine) | 24.19.0-alpine3.24 | 24.22.1-alpine3.24 |
Most third-party images in this release carry the same version as in 1.3.0 but a different digest — they were rebuilt upstream to pick up the patched Node.js and the updated CA bundle. gcr.io/distroless/nodejs24-debian13:nonroot is the clearest case: same tag, different content, and the whole point of the hotfix. Verify what you are running by digest, not by tag. The table below is the record for this release.
Container images in this release
These are the digests pinned by the 1.3.1 chart values at release. They are reproduced here because a hotfix whose substance is a rebuild cannot be identified by version alone; a release notes page is a frozen record rather than a living one. For the general picture of what is deployed and where it comes from, see Container images.
Third-party images
| Image | Version | Digest | Used by |
|---|---|---|---|
quay.io/keycloak/keycloak | 26.7.5 | sha256:37dbaf6f0722c9ec246335f36e1ef8b2e6cb960f7c27e0d8c615121a3d475a85 | keycloak-infra |
quay.io/oauth2-proxy/oauth2-proxy | v7.15.3 | sha256:10a1165743a192e1940b4708fb9647027185ce11a681a1c5519b442ff7f1f561 | auth-proxy |
redis | 7.4.11-bookworm | sha256:4fa24486b8bcca8eec45ee0eb166edc674795e53a2b53d1a9ef263eecebaac85 | auth-proxy |
hashicorp/vault | 2.0.4 | sha256:5be49781ecf78bfe775c5309c6a4d9f4e9e040b6c885c99eb2b12fb69855e1a2 | couchdb, keycloak-infra, keycloak-setup, seaweedfs, vault-infra, vault-secrets-setup |
hashicorp/vault-k8s | 1.7.6 | sha256:55e27b080c9b0469fd420dfb3631243488c6319504b779423caa46c529a95490 | vault-infra |
couchdb | 3.5.2.1 | sha256:5fc596110eac7f412173a7d9de14f70aa5d3e816790fb6e70642755d4a4cf464 | couchdb |
chrislusf/seaweedfs | 4.44 | sha256:e67e8c385484120b78bff47ba5f4debbca47fbd27ed1a39f016f47e8baea615b | seaweedfs |
temporalio/server | 1.31.4 | sha256:1986d4554cc0da8cf09ddcaa10bc348f22f192972b4c2ec1f768f7307c5892e6 | workflow-engine-postgres |
temporalio/admin-tools | 1.31.4 | sha256:c286fe515148587228d692806bc6f7652be5febc384a73dfd16379aed69f7d87 | workflow-engine-postgres |
temporalio/ui | 2.57.0 | sha256:d944f959d0923c35cd991a17a0edbe087770eff843724b181933e0cfdd563ab2 | workflow-engine-postgres — development only; disabled by default in production |
alpine/curl | 8.21.0 | sha256:71597a4f6ac6c7515c77084d2a216aa2f302cd6f9ec311d2f55eb9320f161ce2 | couchdb, seaweedfs |
alpine | 3.22.5 | sha256:14358309a308569c32bdc37e2e0e9694be33a9d99e68afb0f5ff33cc1f695dce | seaweedfs |
alpine/k8s | 1.36.5 | sha256:094adf64cdc4827377cdbe7ea5747472ce115f9fbc64a4e35970ec66777f9a00 | vault-secrets-setup |
docker.io/busybox | 1.38.0 | sha256:dc2d74b28e4cf8984fa52af1f39bc7c3d9c73760b41a74d629f5d11b1ab28616 | keycloak-infra |
Images OLIVE builds
| Image | Version | Digest | Note |
|---|---|---|---|
gcr.io/distroless/nodejs24-debian13 | nonroot | sha256:78f07ef1b5ea71ad7c055df15d0dd8997f2d288f9158623c4d4ae3d765b7d50d | Runtime base image for all Express services. Rebuilt on Node.js 24.22.1 |
gcr.io/distroless/python3-debian13 | nonroot | sha256:727eccc5d83f11273c954652667b5b5a1c66120bd4cfb884e879ab77dcdf966a | Runtime base image for the auth-proxy session-purge job |
node | 24.22.1-slim | sha256:55fb5f5a527ea2c5c4a95f963e48ef90aa38c7b346054fdc8ee9957a2b55d205 | Build stage only, in some services |
node | 24.22.1-alpine3.24 | sha256:06d7adf3e0ef61a13f1d28682726366f97a15aa1888c934d3ecec86c33918b53 | Build stage only, in some services |
job-secrets-image | 0.0.2 | sha256:c3aae17a49bef364cea3da89dd483af6d57492688a9c647340e2374da57e8fe0 | Purpose-built job image published by OLIVE; keycloak-setup, schedule-trigger-cron-job |
Service Versions
Every service and chart carries a new version in this release: the images were rebuilt on patched base images even where the service's own code did not change.
Core Services
| Service Name | Version |
|---|---|
| cloud-function-registry | 2.2.1 |
| instantiator | 1.2.1 |
| data-orchestrator | 3.4.1 |
| file-storage-service | 1.3.1 |
| import-export | 1.2.1 |
| landing-service | 0.3.1 |
| ui-component-registry | 2.3.1 |
| microfrontend-interpreter | 2.3.1 |
| editor | 3.4.1 |
| repository | 1.5.1 |
| scheduler | 1.2.1 |
| session-memory | 1.2.1 |
| template-data-retriever | 0.2.1 |
Extension Services
| Service Name | Version |
|---|---|
| agent-caller | 2.2.1 |
| mcp-server-caller | 0.2.1 |
| prompt-caller | 2.2.1 |
| temporal-caller | 0.2.1 |
| parse-openapi | 0.1.1 |
| develop-support | 0.2.1 |
QA Services
| Service Name | Version |
|---|---|
| ping | 1.2.1 |
| simple-adder | 1.2.1 |
| auth-tester | 0.1.1 |
Infrastructure Charts
| Chart | Version |
|---|---|
| auth-proxy | 0.8.4 |
| certificate | 1.4.2 |
| couchdb | 1.11.2 |
| keycloak-setup | 1.8.2 |
| seaweedfs | 1.5.1 |
| tenant-setup | 1.8.1 |
| vault-secrets-setup | 1.10.2 |
| workflow-engine-postgres | 1.5.3 |
| express (shared library chart behind the Express services) | 2.7.2 |
| schedule-trigger-cron-job | 0.6.3 |
| custom-ca | 0.2.2 |
| utilities (shared Helm library) | 1.13.1 |
Upgrade
1.3.1 upgrades in place from 1.3.0. Point the deployment at the chart versions in Service Versions and sync. There is no export, no redeploy, no data migration and no values change — the breaking changes and the migration procedure in the 1.3.0 release notes are not repeated here, because nothing in this hotfix adds to them.
Two optional follow-ups:
- Re-import the foundational OLIVE Connectivity Bundle if you want the corrected Connectivity Developer Handbook in a tenant. The handbooks ship inside the bundle from 1.3, and the
uiConfigcorrection is part of this release's handbook. Connectivity content is otherwise unaffected. See Import Required Foundational OLIVE Connectivity Bundle. - Correct any
uiConfigauthored withcontrolType, as described under Fixes.
Coming from an earlier release than 1.3.0, work through Migration and Upgrade first and finish on 1.3.1 rather than 1.3.0.
Known gaps
The known gaps listed for 1.3.0 are unchanged by this hotfix. Nothing was closed and nothing was added.
OLIVE 1.3.1 Documentation
The documentation for 1.3.1 is the documentation for OLIVE 1.3 — this manual and the Connectivity Developer Handbook — with the uiConfig field reference corrected as described above.