CVE-2026-130001: Mustache for Ruby: RCE using built-in method access

Critical CVSS 9.8

OSV id
GHSA-5hrj-7fc3-cmx9
Also known as
CVE-2026-130001
Published
Last modified

Affected packages

PackageAffected versionsFixed in
mustache
RubyGems
< 1.1.3 1.1.3

How to fix it

Upgrade mustache to 1.1.3 or later.

bundle update mustache
# make sure the Gemfile allows "mustache", ">= 1.1.3"
  • If it is an indirect dependency, `bundle update` the gem that depends on it.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

Not sure whether your project uses an affected version? Check your lockfile below for free.

Details

[!NOTE] The vulnerability was fully disclosed to the maintainer in private prior to security advisories were enabled for the project. This advisory presents a limited information for initial release to provide a time window for installing updates. Full information with PoCs would be added later.

Summary

Mustache template engine for Ruby in versions 1.1.2 and earlier allows remote attackers to achieve arbitrary code execution through accessing specific built-in methods in an attacker-supplied template.

Details

Mustache is often suggested as a safe simple template language to avoid SSTI vulnerabilities.^1

Mustache for Ruby up to version 1.1.2 did not properly restrict method access which allowed chaining multiple built-in methods to achieve arbitrary code execution.

[!IMPORTANT] Successful exploitation of this vulnerability does not depend on any configuration or objects passed to the template engine. An attacker controlling the template string can achieve arbitrary code execution without any additional requirements.

Additional methods provided by the application or installed gems can further expand the attack surface but exploitation was proven without them.

PoC

All discovered payloads were tested using ruby -e shell commands with mustache as the only explicitly required gem:

ruby -e 'require "mustache"; puts Mustache.render("PAYLOAD GOES HERE", key: "value")'

For initial information release, only the descriptions of the most important discovered payloads would be provided:

  • Universal RCE for a major Ruby version
  • File upload to RCE (3 different payloads)
  • Infinite memory consumption DoS
  • Infinite sleep DoS

Universal RCE payloads for other major Ruby versions and other payloads could exist, as the attack surface is very large. The presented list only contains payloads discovered using a fairly primitive approach.

[!CAUTION] Exploitation is not limited to the discovered Exploits/PoCs and real-life web applications are likely to expose even more dangerous functionality.

Impact

An attacker with the ability to modify the template string can execute arbitrary code in the context of the Ruby application.

Rationale for CVSS assessment:

  • Attack Vector: Network > No network requirements are present for exploitation. > Templating functionality is often provided on public websites.
  • Attack Complexity: Low > Attacker can expect reliable and repeatable exploitation. > There are no requirements beyond attacker's control.
  • Privileges Required: None > Mustache is often used for untrusted user-supplied templates. > Exploitation is often possible without authorization or by using self-registered accounts (without prior privileges). > Mustache by itself does not provide access control functionality.
  • User Interaction: None > Exploitation does not require any user interaction to achieve RCE.
  • Scope: Unchanged > The code is executed with the same privileges as the web application, without changing the scope.
  • Confidentiality Impact: High > Arbitrary code execution leads to the total loss of confidentiality.
  • Integrity Impact: High > Arbitrary code execution leads to the total loss of integrity.
  • Availability Impact: High > Arbitrary code execution can be used to achieve the total loss of availability.

Resources

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.