• /
  • EnglishEspañolFrançais日本語한국어Português
  • Inicia sesiónComenzar ahora

NR26-14: eMudhra Certificate Authority Compromise, Kubernetes Integration

|View as Markdown (English)

Vulnerability Identifier: NR26-14

Priority: High

Summary

Between October 17 and October 20, 2026, researchers disclosed that the private keys for eight intermediate certificate authority (CA) certificates issued by eMudhra can be recovered (CVE-2026-111943). Anyone with those keys can create certificates that software would accept as genuine if it still trusts them. Browsers and operating systems have blocked the certificates, but software that carries its own list of trusted CAs, including some container images, needs to be updated.

New Relic has updated the Kubernetes components below so they no longer accept certificates issued by these CAs. The updated versions are not picked up automatically. Customers need to upgrade to the versions listed below.

Action items

This vulnerability impacts the following components. Customer action necessary for each is as follows:

Component

Fixed version

Customer action

nri-bundle (recommended updating this at a minimum)

Helm chart 8.0.40 (or higher if available)

Run helm repo update, then helm upgrade to 8.0.40

Newrelic-ebpf-agent (if enabled)

1.7.2

Set nr-ebpf-agent.image.tag: "1.7.2" in your values, then helm upgrade. Remove the override once a chart release includes 1.7.2

Newrelic-pixie-integration (if enabled)

2.2.3

Set newrelic-pixie.image.tag: "2.2.3" in your values, then helm upgrade. Remove the override once a chart release includes 2.2.3

If these components are installed separately:

Component (installed separately)

Fixed version

Customer action

newrelic-infrastructure (nri-kubernetes)

Chart: 4.8.0
Images:
- nri-kubernetes:4.9.0
- infrastructure-bundle:3.5.6
- k8s-events-forwarder:1.80.7

Run helm repo update, then helm upgrade to 4.8.0. See the upgrade note*

nri-kube-events

Chart: 3.23.0
Images:
- nri-kube-events:2.23.0
- k8s-events-forwarder:1.80.7

Run helm repo update, then helm upgrade to 3.23.0

nri-metadata-injection

Chart: 4.37.3
Image: k8s-metadata-injection:1.45.3

Run helm repo update, then helm upgrade to 4.37.3

nri-prometheus

Chart: 2.1.25
Image: nri-prometheus:2.30.7

Run helm repo update, then helm upgrade to 2.1.25

newrelic-k8s-metrics-adapter

Chart: 1.21.2
Image: newrelic-k8s-metrics-adapter:0.22.2

Run helm repo update, then helm upgrade to 1.21.2

newrelic-infra-operator

Chart: 3.2.3
Image: newrelic-infra-operator:1.2.3

Run helm repo update, then helm upgrade to 3.2.3

k8s-agents-operator

Chart: 0.54.0
Image: k8s-agents-operator:0.54.0

Run helm repo update, then helm upgrade to 0.54.0

newrelic-prometheus-agent

Chart: 2.14.4
Images:
- newrelic-prometheus-configurator:2.14.4
- prometheus:v3.15.1 (upstream)

Run helm repo update, then helm upgrade to 2.14.4

newrelic-pixie-integration

v2.2.3

Set newrelic-pixie.image.tag: "2.2.3" in your values, then helm upgrade. Remove the override once a chart release includes 2.2.3

newrelic-ebpf-agent

1.7.2

Run helm repo update, then helm upgrade to 1.7.2 when available

Note for all components: If your Helm values pin image tags (for example images.integration.tag), remove the pin or update it to the fixed version. Otherwise the upgrade keeps the old image.

*Upgrade note. newrelic-infrastructure 4.x is a major version. The only breaking change affects Windows nodes. See the chart release notes in the Resources section before upgrading.

Technical vulnerability information

  • Eight intermediate CAs that chain to the emSign ECC Root CA - G3 and, through cross-signing, to AAA Certificate Services, are affected.
  • The fixed Alpine-based images are built on Alpine 3.24.3 with ca-certificates 20261020-r0, which removes emSign ECC Root CA - G3 and AAA Certificate Services from the CA bundle.
    • k8s-agents-operator 0.54.0 is built on a distroless base with both roots removed.
    • prometheus:v3.15.1 (upstream) also ships a CA bundle without either root.
  • New Relic Kubernetes integration binaries are built with Go 1.27.3, whose TLS library refuses certificate chains that contain the eight affected keys, even if the root is still trusted. Some on-host integrations bundled in infrastructure-bundle use earlier Go versions; their CA bundle is still fixed.
  • The exposure is limited to connections that use the public root store: the agents' connections to New Relic endpoints and to any configured proxy. Connections inside the cluster (Kubernetes API server, kubelet, control plane) use the cluster's own CA and aren't affected.

Resources

New Relic has provided the following resources to assist with these updates:

Upgrading

Release notes

Optional components with a manual override

Frequently asked questions

Who can I contact as I still have some questions?

If additional assistance is needed, open a case with our Support team through the help section in the New Relic platform.

Publication history

October 17–20, 2026 - eMudhra intermediate CA certificate compromise disclosed

November 18, 2026 - NR26-14 Published

Copyright © 2026 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.