On this page (7 sections)

On November 20, 2026, the Debian security team published DSA-6644-1, a security update for ruby3.3, the Ruby language interpreter packaged for Debian. The advisory says the fixed issues may result in the execution of arbitrary code, and it assigns the identifier CVE-2026-132825.

If you run Ruby applications on Debian 13 (trixie), such as Rails or Sinatra sites, Jekyll builds, or Ruby scripts on a server, you should check your ruby3.3 package version and update. The advisory is short, so this article also covers what is not yet known.

What Debian has published

The Debian security announcement states that several vulnerabilities were discovered in the Ruby interpreter, which may result in the execution of arbitrary code. For the stable distribution, trixie, the problem is fixed in ruby3.3 version 3.3.14-0+deb13u1, and Debian recommends upgrading your ruby3.3 packages. The advisory points to the Debian security tracker page for ruby3.3 for detailed status.

Note that the advisory lists one CVE identifier while describing several vulnerabilities. The announcement does not explain how the two relate, so check the tracker page for the full list.

What we do not know yet

The advisory is brief, and only this one primary source is available so far. The following are not stated in it:

  • A CVSS score or severity rating.
  • Which Ruby component is affected, or how the bugs are triggered.
  • Whether the flaws are being exploited in the wild.
  • Whether other Debian releases or other Ruby versions are affected. Only trixie is named.
Caution. Do not assume the issue is low risk because no score is published. Debian describes possible arbitrary code execution, so treat the update as a priority for any system that runs Ruby code on untrusted input.

Who is realistically exposed

Arbitrary code execution in an interpreter matters most where Ruby processes data from outside your control. Think of web applications, background job workers, tools that parse uploaded files or fetched content, and CI systems that run Ruby on third-party code. A server that has ruby3.3 installed only as a dependency of some other package and never runs Ruby on external input is less exposed, but it still should be updated through the normal package channel.

The advisory covers the Debian-packaged interpreter. If you install Ruby through other means, such as a version manager, a container image or a vendor bundle, the Debian package update will not change that copy. Check those separately against the upstream Ruby project's guidance.

How to check your exposure

This command lists the installed ruby3.3 package and its version on Debian. Run it on each server; a version older than 3.3.14-0+deb13u1 on trixie means you have not applied the fix.

Show the installed ruby3.3 package version (Debian)Shell
dpkg -l ruby3.3

This query shows the installed and candidate versions from your configured repositories, so you can confirm the fixed version is available to you.

Compare installed and available ruby3.3 versions (Debian)Shell
apt-cache policy ruby3.3

To see which Ruby the shell actually uses, which may differ from the Debian package if a version manager is installed, run:

Show the Ruby binary in use and its versionShell
which ruby && ruby --version

What to do now

  1. Inventory Debian 13 (trixie) hosts and containers that have ruby3.3 installed.
  2. Refresh package lists and upgrade ruby3.3 to 3.3.14-0+deb13u1 or later.
  3. Restart long-running Ruby processes (app servers, job workers) so they load the patched interpreter.
  4. Rebuild and redeploy container images that are based on Debian trixie and include ruby3.3.
  5. Check for Ruby installed outside the Debian package (version managers, vendored runtimes) and update those through their own channels.
  6. Read the Debian security tracker page for ruby3.3 for the full CVE list and status on other releases.

This command updates only the ruby3.3 package to the latest version in your repositories. Run it as root or with sudo, then re-run the version check above.

Update only the ruby3.3 package (Debian trixie)Shell
sudo apt update && sudo apt install --only-upgrade ruby3.3
Caution. Restarting application servers and workers interrupts requests in flight. Schedule the restart in a maintenance window or use your normal rolling restart process.

Detection and follow-up

Because the exploitation status is unknown, review recent behavior on Ruby-running hosts after patching: unexpected child processes spawned by your app server, new files in web or temp directories, and unusual outbound connections. If you suspect compromise, follow our guide on what to do if your website is hacked and the checks in how to tell if a website is hacked.

For a broader view of your public-facing sites, a read-only security scan can flag exposed services and outdated components visible from the outside. It cannot see the Ruby version inside a server, so the package checks above are still needed.

Timeline

Summary
DateEvent
November 20, 2026Debian publishes DSA-6644-1 for ruby3.3, fixed in 3.3.14-0+deb13u1 for trixie
This article will need an update if Debian or the Ruby project publishes more detail, a severity score, or reports of exploitation.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. [SECURITY] [DSA 6644-1] ruby3.3 security updatelists.debian.org ·
  • Debian
  • Ruby
  • DSA
  • patching
  • trixie