dbcve.org
IstioApplication

CVE-2026-41413

HIGH · 7.7 CVSS v3.1 Published 2026-05-07
Fix available
A fix is available. Upgrade to 1.28.6 / 1.29.2 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Istio prior to versions 1.28.6 and 1.29.2, the istiod control plane makes unauthenticated HTTP GET requests to jwksUri endpoints specified in RequestAuthentication resources without validating whether those URLs point to localhost or link-local IP addresses. This allows an attacker with permission to create RequestAuthentication resources to exfiltrate sensitive data by pointing the jwksUri to internal services that would not normally be accessible.

MitigationUpgrade Istio to version 1.28.6, 1.29.2, or later. Until upgraded, avoid using RequestAuthentication resources with jwksUri pointing to internal services, or implement network policies to restrict istiod egress.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IstioApplication
Affected:< 1.28.6>= 1.29.0, < 1.29.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Istio control plane version
    Run 'istioctl version' or check the istiod deployment image version in your cluster
    Affected if Version is less than 1.28.6, or between 1.29.0 and 1.29.1 (inclusive)
  2. Identify RequestAuthentication resources
    Run 'kubectl get requestauthentication -A' to list all RequestAuthentication resources in all namespaces
    Affected if Any RequestAuthentication resources exist in the cluster
  3. Inspect jwksUri configurations
    For each RequestAuthentication resource, run 'kubectl get requestauthentication <name> -n <namespace> -o jsonpath={.spec.jwksUri}' to view the jwksUri value
    Affected if Any jwksUri is configured and points to a URL
  4. Verify jwksUri points to localhost or link-local
    Review the jwksUri values for addresses in the ranges: 127.0.0.0/8, ::1/128, 169.254.0.0/16, or hostnames resolving to these ranges
    Affected if Any jwksUri points to localhost (127.x.x.x), link-local (169.254.x.x), or internal network endpoints not exposed externally

You are affected if your Istio version is in the vulnerable range AND you have RequestAuthentication resources with jwksUri configured pointing to any internal or local endpoints.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.28.6 / 1.29.2 or later
Fixed in 1.28.61.29.2
Interim mitigation

Upgrade Istio to version 1.28.6, 1.29.2, or later. Until upgraded, avoid using RequestAuthentication resources with jwksUri pointing to internal services, or implement network policies to restrict istiod egress.

Recommended fix High confidence

Istio 1.28.6+ or 1.29.2+ (or latest stable release)

  1. 1. Identify the current Istio version running in the cluster using 'istioctl version' or checking the Istio operator deployment
  2. 2. If running Istio version < 1.28.6 or >= 1.29.0 and < 1.29.2, plan for an upgrade
  3. 3. For clusters on 1.28.x: upgrade to Istio 1.28.6 or later (recommended: latest 1.28.x stable)
  4. 4. For clusters on 1.29.0-1.29.1: upgrade to Istio 1.29.2 or later (recommended: latest 1.29.x stable)
  5. 5. Alternatively, upgrade directly to the latest stable Istio release (1.30.x or later)
  6. 6. After upgrade, verify the version with 'istioctl version'
  7. 7. Review any RequestAuthentication resources with jwksUri to ensure they point to appropriate internal endpoints and not localhost (127.0.0.1/::1) or link-local addresses (169.254.0.0/16)
Caveat Patch upgrades typically have minimal breaking changes; review Istio release notes for any deprecation notices

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Istio Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41413 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41413 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data