← Back
CVE-2026-41485
Vulnerability in kyverno (CVE-2026-41485)
Summary
vulnerability in kyverno (CVE-2026-41485). Risk of unauthorized operations or information disclosure. Exploitable via ``forEach``. Mitigation: upgrade to `1.16.4, 1.17.2` or later.
AI summary snake-internal / snake-template-v1
A weakness called CVE-2026-41485 was discovered in Kyverno Controller Denial of.
Severity is Info. Low severity or not yet rated.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "Kyverno Controller Denial of CVE-2026-41485".
CVE-2026-41485 (Kyverno Controller Denial of). Severity: Info. Category: CWE-617.
Response plan:
1. Check the vendor advisory for affected versions and the patched release.
2. If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
3. If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
4. Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
❓ What is the problem
A weakness (CVE-2026-41485) in Kyverno Controller Denial of. A serious software flaw has been identified.
📍 Affected scope
Target versions of Kyverno Controller Denial of (see vendor advisory). If running in production, identify exposure immediately.
🔥 Severity
Severity: Info. Low severity or not yet rated.
🔧 How to fix
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-617)
🛡️ Workaround
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
🔍 Detection
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'kyverno' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `kyverno` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade kyverno to 1.16.4, 1.17.2ステージング環境で 1.16.4, 1.17.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Bitnami
kyverno
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.16.4"},{"introduced":"1.17.0"},{"fixed":"1.17.2"}]}]
Go
github.com/kyverno/kyverno
[{"type":"SEMVER","events":[{"introduced":"1.13.0"},{"fixed":"1.16.4"},{"introduced":"1.17.0-rc.1"},{"fixed":"1.17.2"}]}]
References
- advisory https://github.com/kyverno/kyverno/security/advisories/GHSA-fpjq-c37h-cqcv
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-41485
- package https://github.com/kyverno/kyverno
- patch https://github.com/kyverno/kyverno/commit/76c8fdbe87328722e099e1fd44c3f21c9f7809cb
- patch https://github.com/kyverno/kyverno/commit/80e728c2283a0c65e5adb02d8a907106e6ebe7e3