← Back
CVE-2026-42541
medium
CVSS 4.3
Vulnerability in github.com/kubewarden/kubewarden-controller (CVE-2026-42541)
Summary
vulnerability in github.com/kubewarden/kubewarden-controller (CVE-2026-42541). Risk of unauthorized operations or information disclosure. Exploitable via ``can_i``. Mitigation: upgrade to `1.35.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-42541** has been found in github.com/kubewarden/kubewarden-controller.
Attackers can target a specific entry point like ``can_i`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade github.com/kubewarden/kubewarden-controller to **1.35.0** or later.
If unsure, ask your IT team or search "github.com/kubewarden/kubewarden-controller CVE-2026-42541" on the vendor's site.
CVE-2026-42541 (github.com/kubewarden/kubewarden-controller) — CWE-862 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `can_i` / `list_resources_by_namespace` / `list_resources_all` / `get_resource`
Patched: `1.35.0` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-862) exists in github.com/kubewarden/kubewarden-controller. Attackers reach the vulnerable code path via ``can_i`` without authentication.
📍 Affected scope
github.com/kubewarden/kubewarden-controller — . Attack surface: `can_i` / `list_resources_by_namespace` / `list_resources_all` / `get_resource`.
🔥 Severity
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.35.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/kubewarden/kubewarden-controller' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/kubewarden/kubewarden-controller' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/kubewarden/kubewarden-controller` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/kubewarden/kubewarden-controller to 1.35.0ステージング環境で 1.35.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/kubewarden/kubewarden-controller
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.35.0"}]}]
References
- web https://github.com/kubewarden/adm-controller/security/advisories/GHSA-wqcw-g35j-j578
- web https://github.com/kubewarden/kubewarden-controller/security/advisories/GHSA-wqcw-g35j-j578
- web https://github.com/kubewarden/docs/pull/737
- web https://github.com/kubewarden/kubewarden-controller/pull/1693
- web https://docs.kubewarden.io/howtos/policy-servers/namespaced-policies-capabilities
- web https://nvd.nist.gov/vuln/detail/CVE-2026-42541
- web https://github.com/advisories/GHSA-wqcw-g35j-j578