• /
  • EnglishEspañolFrançais日本語한국어Português
  • EntrarComeçar agora

NR26-17: Ruby2Shell, Ruby Memory Corruption Vulnerability with Potential Remote Code Execution (CVE-2026-132825)

|View as Markdown (English)

Vulnerability Identifier: NR26-17

Priority: Critical

Summary

On November 19, 2026, New Relic's Security Incident Response Team began a comprehensive assessment of our services and enterprise infrastructure against the recently disclosed Ruby vulnerability "Ruby2Shell" (CVE-2026-132825). This is a one-byte heap-based buffer overflow in the Ruby interpreter's string case conversion that could allow remote code execution (RCE) or denial of service (DoS).

Action items

No action required for customers using Ruby agents

New Relic's distributed Ruby agents aren't impacted. New Relic customers who use the Ruby agents don't need to take any action for this vulnerability.

Action required for affected container images

Customer action is required in the following cases:

Component

Fixed version

Customer action

Container image newrelic/newrelic-fluentd-docker

1.20.1
Ruby 3.4.13
Fluentd 1.20.1

Pull the 1.20.1 image or newer and restart containers. Alternatively, you can use Fluentd with the New Relic Fluentd plugin.

Container image newrelic/fluentd

N/A. The image has been deprecated. No fixed version will be released.

Use the newrelic-fluentd-docker image, or build an image with Fluentd and the New Relic Fluentd plugin. Discontinue use of newrelic/fluentd.

Container image newrelic/k8s-golang-apm-linkage-demo

N/A. The image has been removed (end of life). No fixed version will be released.

Stop running and delete any workloads using this image. Remove the image from any internal registries, mirrors, or pull-through caches. No replacement is needed. This was a demo app, not part of the Kubernetes integration, so your monitoring isn't affected.

Technical vulnerability information

Frequently asked questions

  1. Does this affect New Relic's agents?

    The New Relic Ruby language agents aren't affected. Other New Relic language agents are also not affected. The Fluentd images aren't used in the New Relic agents.

  2. Which systems are affected?

    Any container runtime (Kubernetes, Docker, and so on) running the following images:

    • newrelic/newrelic-fluentd-docker
    • newrelic/fluentd
    • newrelic/k8s-golang-apm-linkage-demo
  3. How do I fix the vulnerability?

    If you use the newrelic/newrelic-fluentd-docker image:

    1. Pull the fixed image:

      bash
      $
      docker pull newrelic/newrelic-fluentd-docker:1.20.1
    2. Recreate your containers with the new image. Pulling an image doesn't update containers that are already running. In Kubernetes, Docker, or another container runtime, change the image tag to 1.20.1 and redeploy.

    3. If you build your own images from newrelic/newrelic-fluentd-docker, rebuild them with docker build --pull.

    4. Check the running version:

      bash
      $
      docker exec <container> fluentd --version
    5. The output should show fluentd 1.20.1 or newer.

    If you aren't using the newrelic/newrelic-fluentd-docker image, consider using Fluentd with the New Relic Fluentd plugin.

  4. Is my container updated when I pull a new image?

    No. Running containers keep the old image until you recreate them.

  5. Is the infrastructure agent's log forwarding affected?

    No. Log forwarding in the infrastructure agent and the Kubernetes integration uses Fluent Bit, not Fluentd.

  6. What if I have questions?

    For any support needs related to this communication, open a support case through in-app support.

Publication history

November 21, 2026 - NR26-17 Published

Copyright © 2026 New Relic Inc.

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