VOR Stream 2026.1.6 is the sixth patch release on the v26.1 line and a security release. It moves the bundled secrets store, service registry and message broker to their current releases, strengthens how every service checks sign-in tokens, adds a log of sign-in activity, and updates components across the engine and the web application. Processes, models, studies and screens work as they do on v26.1.5, and the upgrade applies no database migrations.
Highlights
Current releases of Vault, Consul and RabbitMQ
The deployment package includes Vault 2.2, Consul 2.1 and RabbitMQ 4.3, the versions VOR Stream v26.2.0 ships. The releases these replace receive no further security updates in their free editions, and the new versions close the advisories published against them. Existing secrets, policies, service registrations and broker settings carry over; see Third-Party Software for the bundled versions.
Take snapshots before upgrading
Vault 2.2 cannot be returned to the previous version by reinstalling it. Before deploying, save a Vault Raft snapshot and a Consul snapshot, so a rollback can restore them. If your installation keeps RabbitMQ’s data on a separately mounted volume, stop RabbitMQ and empty that volume before upgrading. Nothing is lost: VOR Stream’s queues hold data only while a job runs, and the deployment recreates the broker’s configuration.
Sign-in tokens expire across every service
The compute engine’s REST API and the SDK API check each sign-in token’s validity period, as the web application’s API does, and refuse a token once it expires. The vor command line requests a new token for each command, but a script that reuses a token from vor create token needs a new one after it expires.
A job’s nodes act with the token of the user who started the job, so a job still running when that token expires loses its calls to the engine: signals, dynamic facts, its final log lines, and its statistics. Tokens last 12 hours by default, and about 11 hours for a job started from the web interface. Installations with longer jobs raise vor_token_ttl; see the inventory file reference.
A stronger sign-in library
The library the web application uses to sign users in through an identity provider moves to Authlib 1.9.1, closing eight advisories, the most serious of which let a token with an empty signature pass verification. Identity providers configured as described in Authentication sign users in as before.
A log of sign-in activity
The web application writes one line to django_auth.log in the log directory for each login, failed login and logout, and for each API call whose token it refuses. A line holds the time, the event, the sign-in method (identity provider, password or API token), the user, the reason a sign-in failed, and the client address. The log answers where login events are recorded; see Auth Log for the fields and reason codes, and Log Files for every file in the log directory.
Rotate the file without loosening it
A user who types a password into the username field leaves it in a failed-login line, so the playbooks create django_auth.log readable only by vor_user and vor_group. Nothing rotates the file; Log Files explains how to rotate it and keep that mode.
Security
The release also includes these updates:
- The Go toolchain moves to 1.27.3, which closes standard-library advisories and stops trusting intermediate certificates whose private keys were compromised. The engine’s networking and spreadsheet libraries move to their patched releases, so a crafted workbook uploaded through the SDK cannot crash or stall the service.
- The SDK API answers a malformed sign-in token with a refusal, and the web application answers an expired, invalid or malformed token with a refusal.
- Django moves to 5.2.18 and Django REST Framework to 3.18.3, closing advisories that let a crafted request consume excessive processing time or be decoded with an unexpected character encoding.
- The Erlang/OTP runtime that RabbitMQ runs on moves to 27.3.4.19.
- The Python interpreter in the deployment package moves to 3.11.18, which includes the security fixes released since 3.11.4.
- With TLS on, the message broker accepts only TLS 1.3 connections, so a client cannot renegotiate a connection once it is established. Security scans that report TLS renegotiation (CVE-2009-3555) on the broker’s ports no longer find it.
- The web server moves to Caddy 2.11.7.
- The HTTP, certificate and DNS libraries in the web application and the compute environment move to their patched releases, along with the Angular framework.
Every update is checked against the project’s dependency scanners before release.
Administration & Deployment
Upgrading in place. The deployment playbooks upgrade Vault, restart it on the new release and unseal it in the same run. Consul servers upgrade on the next run with a setting that keeps connections between Consul agents stable; keep port 8300 open only to Consul agents, as Ports describes. RabbitMQ upgrades with the settings the engine’s queues need. A deployment that also upgrades Erlang/OTP restarts the broker before it enables plugins.
Auth log configuration. The playbooks configure django_auth.log. An installation that maintains the web application’s logging configuration outside the playbooks takes the auth-log entries from the deployment’s template and creates the file with mode 0640 before the application starts.
Go 1.27.3. Compute hosts receive Go 1.27, which playpens use to build Go nodes and models, and the playpen template moves to go 1.27. Go 1.27 keeps the Go 1 compatibility promise, so existing node and model code should build unchanged; report a build failure after upgrading. The Third-Party Software page lists the bundled versions.
Offline Ansible bundle. The offline bundle in the deployment package holds ansible-core 2.16 and the five collections the playbooks call (amazon.aws, community.general, community.hashi_vault, community.postgresql and community.rabbitmq), at the versions Ansible 9 included. The bundle is smaller and contains only what the playbooks run. setup-ansible-offline.sh runs as before; playbooks of your own that use other collections need those collections installed separately.
Compute host SSH. On hosts with OpenSSH 9.8 or later, the compute host’s SSH service penalized the address of Consul’s health check after a restart, which on a single-host installation is also the engine’s address. The playbooks configure the service to skip that one penalty. It keeps throttling failed logins and other abuse.
Python 3.11.18. The deployment playbooks rebuild Python and the virtual environments that the engine and the web application use on each host, so Python nodes on a host are unavailable until its deployment finishes. Upgrade outside job run windows. Playpen virtual environments keep working with the packages they hold; run venv/bin/python -m venv –upgrade venv in a playpen to move its environment to 3.11.18. The version comes from the deployment package, so a Python_version line in an existing inventory file is ignored. The Third-Party Software page lists the bundled versions.
Credential and certificate procedures. New administration guides cover changing stored passwords for database node connections, the application database, and RabbitMQ, and rotating Consul TLS certificates. Each guide gives the order of steps, the services to restart, and how to confirm the change.
Replace the packaged Consul certificate authority
The Consul certificate authority supplied with the deployment package expires on May 3, 2027. Installations that use it should create their own, as Replacing the CA describes.
Upgrade Notes
Review before upgrading
v26.1.6 applies no database migrations, but the Vault upgrade is one-way and expired sign-in tokens are refused. Take the snapshots described above, and raise vor_token_ttl if jobs can run longer than about 11 hours.
Python is rebuilt during the upgrade, so schedule it outside job run windows. Python’s email.utils.parseaddr returns an empty address for malformed input, where earlier versions returned a wrong one; a node that parses addresses with it should expect the empty result.
The web server refuses requests whose headers exceed 16 KiB. An unusually large sign-in token from an identity provider is the case to check.
With TLS on, the message broker refuses TLS 1.2 connections. A reverse proxy or load balancer that forwards the RabbitMQ management port, as Deploying VOR Stream Behind a Reverse Proxy describes, must connect to the broker with TLS 1.3. On an AWS Application Load Balancer, give one of its HTTPS listeners a TLS 1.3 security policy, such as the one that page recommends.
An identity provider that marks its tokens as not supporting a nonce, and omits the nonce, is refused at sign-in. Providers that follow the OpenID Connect specification include the nonce.
Playpens upgrade when the service first starts on the new version. On an installation that has disabled automatic upgrades, or for a playpen whose upgrade reports an error, run vor update playpen against the playpen directory.