Koios Automation Platform 2026.11.1 — release notes
Security update of 2026.11.0, published 2026-10-31 in the private registry ghcr.io/koiosplatform.
Catalog:
ghcr.io/koiosplatform/koios-operator-catalog@sha256:f374a782eb38328b28edaee8d998d9d49c11d8469a39a11e2f47b92fcb11fca9
(see olm-install.md).
Upgrading from 2026.11.0
Point the koios-operators CatalogSource at the new catalog digest. OLM upgrades the operators in the
stable-2026.11 and stable-2026.11-cluster-scoped channels (koios-operator.v2026.11.1 replaces
v2026.11.0); with installPlanApproval: Manual, approve the InstallPlan. The operators then roll
the platform to the 2026.11.1 images. No data migration and no KoiosPlatform changes are needed.
What changed
Same component versions and features as 2026.11.0; only the images are rebuilt:
System packages updated in every image. Operators use pinned, signature-checked UBI 9 RPMs.
Envoy 1.36.6 → 1.36.13.
Python dependency security updates in the controller, gateway, EDA, hub, execution environment and operators (for example aiohttp, cryptography, Django 5.2.17, oauthlib, PyJWT, pyasn1, urllib3), every image checked with
pip check.ansible-operatorv1.42.3 andreceptorv1.6.9 rebuilt at the same versions with Go 1.26.10 and updatedgolang.org/xmodules.Automation hub no longer ships upstream development profiles and keys (
/app/profiles,/app/dev).
No image has CRITICAL findings left.
Known remaining findings
Updates blocked by upstream version caps: Django REST framework and
cryptography≥ 47 (django-ansible-base), aiohttp in automation hub (pulpcore),social-auth-core5 in hub,cryptography48 in the execution environment (msal), Twisted (release candidate only).Decision environment: jackson inside the
drools_jpy0.4.1 jar, the latest upstream release.