Skip to content
VulniPulse
Sign in
Advisory severityMedium6.8Veeam Updated

Medium [CVE-2026-111943] Mitigating Impact of Compromised eMudhra Intermediate CA Certificates on Veeam Kasten for Kubernetes

This medium-severity Veeam advisory covers CVE-2026-111943.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

KB4954 Source published

VulniPulse record published Record updated

CVE-2026-111943
Related products & platforms
VeeamBackup & ReplicationKasten
Open source advisory

Get an email when Veeam publishes the next one.

VulniPulse checks Veeam's security advisories around the clock and emails you new ones with the severity, the fixed version and the vendor's link. First month free, then US$15/month; we email you before the first charge.

Start your free month

Summary

Mitigating Impact of Compromised eMudhra Intermediate CA Certificates on Veeam Kasten for Kubernetes

KB ID: 4954

Product:

Published: 2026-10-22

Last Modified:

Issue Summary

Until these intermediates are blocked, anyone holding a recovered key can issue certificates that TLS clients trust. According to eMudhra's statement on the incident, none of the affected intermediates issued any certificates, and eMudhra is not aware of any evidence that the weak keys were exploited before the issue was disclosed.

How This Impacts Veeam Kasten for Kubernetes

Veeam Kasten for Kubernetes components use TLS to connect to the following external endpoints:

  • Object storage and cloud provider storage APIs
  • OIDC and LDAPS identity providers
  • Veeam Backup & Replication
  • Veeam Data Cloud Vault
  • Cloud marketplace metering APIs
  • The Kasten telemetry service
  • The public Kasten Helm chart index (used for update notifications)

An attacker who can intercept that traffic could impersonate one of these endpoints without causing a certificate error.

Veeam Kasten for Kubernetes verifies certificates against the trust store inside its containers. Updating the operating system of the Kubernetes nodes does not change that trust store, so the issue is resolved only by upgrading Veeam Kasten for Kubernetes.

Veeam Kasten for Kubernetes 9.0.9 addresses this issue in two ways:

Affected versions
  • 9.0.8
  • 1.27.3
  • 1.27.2

Official advisory · high-confidence parse· fetched 1 day ago·verify at source

Fixed versions
  • 9.0.9

Official advisory · high-confidence parse· fetched 1 day ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Upgrade to Veeam Kasten for Kubernetes 9.0.9 or later, which contains the listed security fixes.

Official advisory · high-confidence parse· fetched 1 day ago·verify at source

More Veeam advisories

All Veeam advisories

Android app · Google Play

Monitor future Veeam CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Get CVE alertsSee app features

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.