CVE-2026-130001

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-11-18. The CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, GitHub Security Advisory

Also known asGHSA-5hrj-7fc3-cmx9 (GitHub Security Advisories)

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fixed version is listed under Patch Availability — apply it.

Mustache for Ruby: RCE using built-in method access

> [!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] [^2]

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

[^1]: https://portswigger.net/knowledgebase/papers/serversidetemplateinjection.pdf [^2]: https://hackerone.com/reports/423541

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0% × 40%
No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fixed version is listed under Patch Availability. Apply it within your standard update timelines.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
Unknown (no EPSS on record)Unknown, not low: FIRST has published no EPSS probability for this CVE.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fixed version is listed under Patch Availability. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 18, 2026

Last Modified

November 18, 2026

Vendor Advisories for CVE-2026-130001(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
rubygemsmustache @ 1.1.3 (fixes <= 1.1.2)—ghsa

These rows come from GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 4× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 20:39 UTCGHSA enrichmentGHSA-5hrj-7fc3-cmx9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-11-20 19:21 UTCGHSA enrichmentGHSA-5hrj-7fc3-cmx9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-19 18:03 UTCGHSA enrichmentGHSA-5hrj-7fc3-cmx9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-18 16:46 UTCEchelonGraph re-scoredFirst assessed: 9.8 CRITICAL
  5. 2026-11-18 16:46 UTCGHSA enrichmentGHSA-5hrj-7fc3-cmx9 · GitHub severity CRITICAL · GitHub CVSS 9.8

Frequently asked(4)

What is CVE-2026-130001?
CVE-2026-130001 is a critical-severity vulnerability; its CVE record was published on November 18, 2026. Mustache for Ruby: RCE using built-in method access [!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.…
When was the CVE record for CVE-2026-130001 published?
The CVE record for CVE-2026-130001 was published on November 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 18, 2026; the record at its source may have been updated since.
What is the CVSS score of CVE-2026-130001?
CVE-2026-130001 has a CVSS base score of 9.8 (the CNA's own assessment, by github_m; NVD's own analysis pending).
How do I remediate CVE-2026-130001?
A fixed version for CVE-2026-130001 is listed under Patch Availability on this page: update to the version listed for your package. The vendor advisories EchelonGraph has for CVE-2026-130001 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-130001

Explore →

Is Your Infrastructure Affected by CVE-2026-130001?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.