SSRF (Server-Side Request Forgery) in istio.io/istio (CVE-2026-41413)
Summary
SSRF in istio.io/istio (CVE-2026-41413). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.0.0-20260410004459-189832a289c1 or later.
Original description
The description as published by the source.
Istio is an open platform to connect, manage, and secure microservices. Prior to versions 1.28.6 and 1.29.2, when a RequestAuthentication resource is created with a jwksUri pointing to an internal service, istiod makes an unauthenticated HTTP GET request to that URL without filtering out localhost or link local ips. This can result in sensitive data being distributed to Envoy proxies via xDS configuration. This issue has been patched in versions 1.28.6 and 1.29.2.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A weakness called CVE-2026-41413 was discovered in istio.io/istio.
In plain terms, it is an SSRF flaw that lets attackers probe internal networks.
Severity is Medium (CVSS 5/10). Exploitation requires specific conditions but can cause real harm if successful.
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 "istio.io/istio CVE-2026-41413".
CVE-2026-41413 (istio.io/istio). Severity: Medium / CVSSv3 5. Category: CWE-918.
Response plan:
- Check the vendor advisory for affected versions and the patched release.
- If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
- If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
- Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
A weakness (CVE-2026-41413) in istio.io/istio. In plain words, it is an SSRF flaw that lets attackers probe internal networks.
Target versions of istio.io/istio (see vendor advisory). If running in production, identify exposure immediately.
Severity: Medium (CVSS 5/10). Exploitation requires specific conditions but can cause real harm if successful.
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-918)
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'istio.io/istio' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
istio.io/istioを grep し、稼働しているサービス・バージョンを把握する。 -
5Apply temporary workaround mitigate
Users can deploy a `ValidatingAdmissionPolicy` to prevent the creation of `RequestAuthentication` resources with suspicious jwksUri field values (e.g.パッチが適用されるまでの応急処置として、Users can deploy a
ValidatingAdmissionPolicyto prevent the creation ofRequestAuthenticationresources with suspicious jwksUri field values (e.g. を実施。回避策の副作用 (機能低下) を確認した上で。 -
6Apply patch patch
Upgrade istio.io/istio to 0.0.0-20260410004459-189832a289c1ステージング環境で 0.0.0-20260410004459-189832a289c1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com