Skip to content

Commit 85146e8

Browse files
authored
Merge branch 'main' into docs/apps-extra-categorization
2 parents 96801f1 + 405557d commit 85146e8

21 files changed

Lines changed: 590 additions & 179 deletions

File tree

‎.github/workflows/fetch-telemetry.yml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,12 +19,12 @@ jobs:
1919
runs-on: ubuntu-latest
2020
steps:
2121
- name: Checkout repository
22-
uses: actions/checkout@v4
22+
uses: actions/checkout@v7
2323
with:
2424
ref: 'main'
2525

2626
- name: Set up Python
27-
uses: actions/setup-python@v5
27+
uses: actions/setup-python@v6
2828
with:
2929
python-version: '3.12'
3030

‎.github/workflows/hugo.yaml‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -41,13 +41,13 @@ jobs:
4141
- name: Install Dart Sass
4242
run: sudo snap install dart-sass
4343
- name: Checkout
44-
uses: actions/checkout@v4
44+
uses: actions/checkout@v7
4545
with:
4646
submodules: recursive
4747
fetch-depth: 0
4848
- name: Setup Pages
4949
id: pages
50-
uses: actions/configure-pages@v4
50+
uses: actions/configure-pages@v6
5151
- name: Install Node.js dependencies
5252
run: "[[ -f package-lock.json || -f npm-shrinkwrap.json ]] && npm ci || true"
5353
- name: Download OpenAPI specs
@@ -71,7 +71,7 @@ jobs:
7171
echo -e "\nDisallow: /" >> public/robots.txt
7272
cat public/robots.txt
7373
- name: Upload artifact
74-
uses: actions/upload-pages-artifact@v3
74+
uses: actions/upload-pages-artifact@v5
7575
with:
7676
path: ./public
7777

@@ -85,5 +85,5 @@ jobs:
8585
steps:
8686
- name: Deploy to GitHub Pages
8787
id: deployment
88-
uses: actions/deploy-pages@v4
88+
uses: actions/deploy-pages@v5
8989

‎.github/workflows/update-oss-health.yaml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,12 +19,12 @@ jobs:
1919

2020
steps:
2121
- name: Checkout target repo
22-
uses: actions/checkout@v4
22+
uses: actions/checkout@v7
2323
with:
2424
ref: 'main'
2525

2626
- name: Setup Python
27-
uses: actions/setup-python@v5
27+
uses: actions/setup-python@v6
2828
with:
2929
python-version: '3.12'
3030

448 KB
Loading
Lines changed: 99 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,99 @@
1+
---
2+
title: "Security Advisory — CVE-2026-53359 (\"Januscape\"): KVM Guest-to-Host Escape"
3+
slug: security-advisory-cve-2026-53359-januscape-kvm-guest-to-host-escape
4+
date: 2026-07-08
5+
author: "Cozystack Team"
6+
description: "CVE-2026-53359 (\"Januscape\") is a KVM guest-to-host escape affecting all current Talos kernels. Cozystack clusters that run VMs or tenant Kubernetes should disable nested virtualization now."
7+
images:
8+
- "cve-2026-53359-banner.png"
9+
article_types:
10+
- announcement
11+
topics:
12+
- security
13+
- virtualization
14+
---
15+
16+
{{< figure src="cve-2026-53359-banner.png" alt="Security advisory banner — CVE-2026-53359 Januscape KVM guest-to-host escape" width="720" >}}
17+
18+
**Severity:** High for clusters running virtualization. **Status:** No fixed Talos release yet — mitigation required now.
19+
20+
## What happened
21+
22+
On 2026-07-06 a Linux kernel vulnerability, **CVE-2026-53359** ("Januscape"), was publicly disclosed together with a working exploit. It is a use-after-free in the KVM/x86 shadow MMU that lets a **guest VM break out to its host** (the cluster node) or crash the node's kernel. It affects both Intel and AMD CPUs and has been latent in the kernel since 2010.
23+
24+
The upstream fix shipped in stable kernels (6.18.38, 6.12.95, 6.6.144, 6.1.177, 7.1.3) on 2026-07-04, but **Talos Linux has not yet released an image with the fixed kernel.** Every current Talos version still runs a vulnerable kernel.
25+
26+
## Who is affected
27+
28+
Cozystack installations that run **virtualization or tenant Kubernetes clusters** — tenant Kubernetes nodes are KubeVirt VMs, so they count. If you run only containerized workloads and never create VMs or tenant clusters, your exposure is much lower.
29+
30+
## The risk
31+
32+
The exploit needs two things a tenant already has: root inside their own VM, and nested virtualization exposed to the guest (on by default). A malicious tenant could then:
33+
34+
- crash the node kernel, taking down every co-tenant VM on that node (denial of service), or
35+
- with a working exploit, run code on the node and compromise the cluster.
36+
37+
KubeVirt's sandboxing (unprivileged containers, seccomp, SELinux) does **not** stop this — the bug is in the host kernel and is reached through the normal KVM interface every VM must use.
38+
39+
## Recommended mitigation: disable nested virtualization
40+
41+
Cozystack VMs do not need nested virtualization. Disabling it removes the attack surface entirely, regardless of kernel version.
42+
43+
### Talos (most clusters)
44+
45+
Add to your Talos machine config, under `machine.install`:
46+
47+
```yaml
48+
machine:
49+
install:
50+
# Talos >= 1.12 only: pin grubUseUKICmdline false so the args are applied
51+
# (otherwise they are silently ignored on UEFI/UKI systems).
52+
grubUseUKICmdline: false
53+
extraKernelArgs:
54+
- kvm_intel.nested=0
55+
- kvm_amd.nested=0
56+
```
57+
58+
Both lines are safe on Intel and AMD — the one that does not match your CPU is ignored. On Talos **older than 1.12** the `grubUseUKICmdline` field does not exist and `extraKernelArgs` is ignored on UEFI/UKI nodes; there the args must be baked into the boot image via Image Factory.
59+
60+
**Apply it in two steps — `talm apply`, then `talm upgrade`.** First push the updated machine config to the node, then re-run the Talos installer so the kernel arguments are written into the boot configuration (a plain `talm apply` alone does not rewrite the boot config). You can upgrade to the *same* Talos version you are already on — the point is to re-run the installer with the new arguments:
61+
62+
```bash
63+
# 1. Push the updated machine config to the node
64+
talm apply -f nodes/<node>.yaml
65+
66+
# 2. Re-run the installer so the kernel args land in the boot config (this reboots the node)
67+
talm upgrade -f nodes/<node>.yaml
68+
```
69+
70+
**Warning: this reboots the node.** Roll it out **one node at a time**, waiting for each node to become `Ready` (and for etcd quorum to recover on control-plane nodes) before moving to the next.
71+
72+
### Generic Linux hosts (non-Talos)
73+
74+
Create `/etc/modprobe.d/cozystack-kvm-nested.conf`:
75+
76+
```
77+
options kvm_intel nested=0
78+
options kvm_amd nested=0
79+
```
80+
81+
Then reboot the node (or reload the `kvm` module) for it to take effect.
82+
83+
## Automation
84+
85+
We have updated our Cozystack Claude Code skills to prescribe and verify this mitigation during bootstrap and upgrades, so the setting is placed under `machine.install` and persists across future Talos upgrades: [cozystack/ccp#17](https://github.com/cozystack/ccp/pull/17).
86+
87+
You can use the `cozystack:talos-bootstrap` and `cozystack:cluster-upgrade` skills to apply and verify the change automatically.
88+
89+
## After a fixed Talos ships
90+
91+
Once Talos releases an image with the patched kernel (6.18.38 or newer), upgrade normally. You may keep nested virtualization disabled as a hardening measure, or re-enable it (remove the two arguments) if a specific workload requires it. We will notify you when a fixed Talos release is available.
92+
93+
## Join the community
94+
95+
* GitHub: [cozystack/cozystack](https://github.com/cozystack/cozystack)
96+
* Telegram: [@cozystack](https://t.me/cozystack)
97+
* Slack: [#cozystack](https://kubernetes.slack.com/archives/C06L3CPRVN1) on the Kubernetes workspace ([invite](https://slack.kubernetes.io))
98+
* [Subscribe to our community meetings calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/cozystack)
99+
* [Add meetings to your calendar](https://webcal.prod.itx.linuxfoundation.org/lfx/lfsixxnFWxbvsyEuC2)

‎content/en/docs/next/applications/external.md‎

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,7 @@ An external application repository has the following layout:
2323
init.yaml # Bootstrap manifest (GitRepository + HelmRelease)
2424
scripts/
2525
package.mk # Shared Makefile targets for app charts
26+
update-appdef.sh # Syncs generated chart schemas into the ApplicationDefinitions
2627
packages/
2728
core/platform/ # Platform chart: namespaces, operators, HelmCharts, ApplicationDefinitions
2829
apps/<app-name>/ # Helm chart for each user-installable application
@@ -99,7 +100,7 @@ spec:
99100
sourceRef:
100101
kind: HelmRepository
101102
name: <operator-name>
102-
version: '>=1.0.0'
103+
version: '1.2.3' # pin an exact operator version to keep installs reproducible
103104
```
104105

105106
### ApplicationDefinitions
@@ -123,7 +124,7 @@ spec:
123124
name: external-apps-<app-name>
124125
namespace: cozy-public
125126
labels:
126-
cozystack.io/ui: "true"
127+
sharding.fluxcd.io/key: tenants
127128
prefix: <app-name>-
128129
dashboard:
129130
category: <Category>
@@ -155,7 +156,7 @@ Follow these naming conventions (matching the main Cozystack repository):
155156
| `release.prefix` | `<metadata.name>-` | `my-app-` |
156157
| `openAPISchema` title | always `"Chart Values"` | — |
157158

158-
The `openAPISchema` field contains a single-line JSON string with the schema for the application values. It intentionally omits `if`/`then`/`else` conditional rules because Kubernetes `apiextensions/v1` `JSONSchemaProps` does not support these keywords. Use conditional validation only in the Helm chart's `values.schema.json`.
159+
The `openAPISchema` field contains a single-line JSON string with the schema for the application values — the minified content of the chart's generated `values.schema.json`. Keep the two in sync: in the example repository, `make generate` embeds the schema with `scripts/update-appdef.sh`. Note that Kubernetes `apiextensions/v1` `JSONSchemaProps` does not support `if`/`then`/`else`, so schemas must not rely on conditional validation.
159160

160161
## Application Charts
161162

@@ -191,11 +192,16 @@ export NAME=<app-name>
191192
export NAMESPACE=external-<operator-name>
192193
193194
include ../../../scripts/package.mk
195+
196+
.PHONY: generate
197+
generate:
198+
cozyvalues-gen -v values.yaml -s values.schema.json -r README.md
199+
../../../scripts/update-appdef.sh $(NAME)
194200
```
195201

196202
### values.schema.json
197203

198-
Define the JSON Schema (draft-07) for the application values. This schema is used by Helm for validation at install time and can include conditional rules (`if`/`then`/`else`) that are not supported at the `ApplicationDefinition` level.
204+
Generate the JSON schema from annotations in `values.yaml` with [`cozyvalues-gen`](https://github.com/cozystack/cozyvalues-gen) — the same tool and annotation dialect used for packages in the main Cozystack repository. Helm validates user-supplied values against this schema at install time. Run `make generate` after changing `values.yaml` and commit the regenerated files.
199205

200206
## Bootstrap Manifest
201207

‎content/en/docs/next/development.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -247,9 +247,9 @@ This structure simplifies upstream chart updates.
247247
└── values.schema.json # JSON schema used for input values validation and to render UI elements in dashboard
248248
```
249249

250-
You can use bitnami's [readme-generator](https://github.com/bitnami/readme-generator-for-helm) for generating `README.md` and `values.schema.json` files.
250+
Use [`cozyvalues-gen`](https://github.com/cozystack/cozyvalues-gen) to generate the `README.md` parameters table and the `values.schema.json` schema from annotations in `values.yaml`.
251251

252-
Just install it as `readme-generator` binary in your system and run generation using `make generate` command.
252+
Install the `cozyvalues-gen` binary from [the releases page](https://github.com/cozystack/cozyvalues-gen/releases) and run `make generate` in the package directory. Besides the schema and the README, it also refreshes the package's `ApplicationDefinition` (`spec.application.openAPISchema` and `spec.dashboard.keysOrder`) via `hack/update-crd.sh`.
253253

254254
## Helm Chart Development Principles
255255

‎content/en/docs/next/install/kubernetes/talm.md‎

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -95,6 +95,7 @@ The structure of the project mostly mirrors an ordinary Helm chart:
9595
- `secrets.encrypted.yaml`, `talosconfig.encrypted` - encrypted counterparts produced from `talm.key` (commit these to git instead of the plaintext files).
9696
- `talm.key` - the project-local age key used for encrypt / decrypt. Back this up; without it the encrypted files cannot be reopened.
9797
- `values.yaml` - a common values file used to provide parameters for the templating.
98+
- `.talm-preset.lock` - a machine-managed file recording the preset name and its content hash at init time; used to detect preset drift after a talm binary upgrade. Commit it to git so the baseline is shared across the team.
9899
- `nodes` - an optional directory used to describe and store generated configuration for nodes.
99100

100101
#### Available Presets
@@ -151,6 +152,17 @@ talm init --update --preset cozystack # interactive: prompts for each p
151152
talm init --update --preset cozystack --force # non-interactive: auto-accept all diffs
152153
```
153154

155+
`--update` re-syncs the vendored `charts/talm/` exactly — files that the new library no longer ships (or strays like `.DS_Store`) are pruned — and advances the preset baseline in `.talm-preset.lock`.
156+
157+
#### Chart Drift Detection (Talm v0.32+)
158+
159+
Render commands read the project's local `charts/talm/` copy, never the binary's built-in charts, so upgrading the talm binary does not touch your project — the vendored chart silently goes stale. Release builds of talm detect this and print a non-fatal `WARN:` line on stderr for two independent signals:
160+
161+
- **Library drift**: the vendored `charts/talm/` differs by content from the copy built into the binary. A pure version stamp difference stays silent; a real difference is reported with a sample of the differing paths (`modified:` / `extra:` / `missing:`).
162+
- **Preset drift**: the binary ships a newer preset than the baseline pinned in `.talm-preset.lock` at init time. Your `templates/` edits are never reported as drift — the comparison is binary-vs-baseline, not binary-vs-project.
163+
164+
Both warnings point at the remediation above. To escalate the warning into a hard error (exit 1) — for example, in CI — set `strictCharts: true` in `Chart.yaml` so the whole team inherits it, or pass `--strict-charts` for a single run. Under strict mode, a baseline that cannot be verified (a corrupted or deleted `.talm-preset.lock`, an unreadable `charts/talm/`) also blocks, so deleting the baseline is not a bypass; without strict mode, such failures degrade to a warning, and projects created before baseline pinning stay silent.
165+
154166
#### Encrypt / Decrypt Round-Trip
155167

156168
The encrypted copies are what you commit to git; the plaintext copies are what `talm` reads. Use these to round-trip between the two:
@@ -258,6 +270,45 @@ To configure Keycloak as an OIDC provider, apply the following changes to the te
258270
```
259271
260272
273+
### 2.4 Encrypted user values and secret redaction (Talm v0.32+)
274+
275+
Beyond `secrets.yaml` (the Talos bootstrap secrets), templates often inject operator-supplied secrets into the config — a registry password, an OIDC client secret, a static-pod env value. Talm lets you keep those encrypted in git the same way as `secrets.yaml`, decrypt them in memory at render time, and keep them out of committed node files, terminal output, and CI logs.
276+
277+
**Step 1 — put the secret values in `values-secret.yaml`:**
278+
279+
```yaml
280+
registryPassword: "s3cr3t-high-entropy-value"
281+
```
282+
283+
**Step 2 — encrypt it** with the project's `talm.key`. `talm init --encrypt` produces `values-secret.encrypted.yaml`. Commit the encrypted file; the plaintext `values-secret.yaml` is git-ignored.
284+
285+
**Step 3 — reference the encrypted file** from `Chart.yaml` by adding it to `templateOptions.valueFiles`, so both `talm template` and `talm apply` read it:
286+
287+
```yaml
288+
templateOptions:
289+
valueFiles:
290+
- values-secret.encrypted.yaml
291+
```
292+
293+
Referencing it only via the CLI `--values` flag is a foot-gun: the modeline in a node file does not persist value files, so a later `talm apply` would re-render WITHOUT the secret and silently drop the field. Talm surfaces a warning when an encrypted file is passed via `--values` but is not in `templateOptions.valueFiles`.
294+
295+
**Step 4 — use the values in templates** like any other: `{{ .Values.registryPassword | quote }}`.
296+
297+
How secrets are handled across commands:
298+
299+
| Command | Behavior |
300+
| --- | --- |
301+
| `talm template` (stdout) | secret values render as `***`; `--show-secrets` prints them verbatim. |
302+
| `talm template -I` (node file) | secret values are omitted entirely from the committed node file — the real value is re-rendered in memory only at apply, so no plaintext (or ciphertext) ever lands in `nodes/*.yaml`. |
303+
| `talm apply --dry-run` | both diffs redact secrets: talm's structured drift preview AND the server-returned `Config diff:` block. `--show-secrets-in-drift` reveals them. |
304+
305+
The `--show-secrets-in-drift` flag governs every secret-bearing surface of the apply dry-run, covering both these user values and the Talos bootstrap material (`cluster.ca.key`, `machine.token`, encryption secrets, Wireguard keys, etc.). By default, a dry-run never prints a CA private key or a user secret in cleartext.
306+
307+
`talm apply` honors the full set of value sources, matching `talm template`: `--values`, `--set`, `--set-string`, `--set-file`, `--set-json`, `--set-literal`, merged on top of the `templateOptions.*` defaults from `Chart.yaml`. This keeps `template` and `apply` rendering identically.
308+
309+
**Sharp edge — value-based matching.** Redaction matches by exact value across the whole rendered config, so a secret whose plaintext coincides with an ordinary structural string (a password literally set to `controlplane`, or a bare port like `6443`) will also redact that unrelated field. Prefer high-entropy values; do not encrypt low-entropy strings that collide with non-secret config.
310+
311+
261312
## 3. Generate Node Configuration Files
262313
263314
Next step is to make node configuration files from templates.

‎content/en/docs/next/install/kubernetes/talos-bootstrap.md‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -102,6 +102,10 @@ talos-bootstrap --help
102102
- 10.96.0.0/16
103103
```
104104

105+
{{% alert title="Do not change op: on these entries" color="warning" %}}
106+
Talos rejects `op: create` for any file outside `/var`, returning the error `create operation not allowed outside of /var` — the only exception is the special-cased `/etc/cri/conf.d/20-customization.part`. Because `/etc/lvm/lvm.conf` already exists on the node, it must use `op: overwrite`. Changing the op (or pointing `create` at another `/etc` path) fails the `WriteUserFiles` boot step: the node pauses and enters a reboot loop, and `talosctl bootstrap` reports only `bootstrap is not available yet` with no obvious cause.
107+
{{% /alert %}}
108+
105109
1. Make another configuration patch file `patch-controlplane.yaml` with settings exclusive to control plane nodes:
106110

107111
```yaml

‎content/en/docs/next/install/kubernetes/talosctl.md‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -126,6 +126,10 @@ Discovered open port 50000/tcp on 192.168.123.13
126126
- 10.96.0.0/16
127127
```
128128

129+
{{% alert title="Do not change op: on these entries" color="warning" %}}
130+
Talos rejects `op: create` for any file outside `/var`, returning the error `create operation not allowed outside of /var` — the only exception is the special-cased `/etc/cri/conf.d/20-customization.part`. Because `/etc/lvm/lvm.conf` already exists on the node, it must use `op: overwrite`. Changing the op (or pointing `create` at another `/etc` path) fails the `WriteUserFiles` boot step: the node pauses and enters a reboot loop, and `talosctl bootstrap` reports only `bootstrap is not available yet` with no obvious cause.
131+
{{% /alert %}}
132+
129133
1. Make another configuration patch file `patch-controlplane.yaml` with settings exclusive to control plane nodes:
130134

131135
Note that VIP address is used for `machine.network.interfaces[0].vip.ip`:

0 commit comments

Comments
 (0)