CVE-2026-41316

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.1%, top 37% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.1Exploit: None knownExposed: 0

A fix is available — apply it.

ERB is a templating system for Ruby. Ruby 2.7.0 (before ERB 2.2.0 was published on rubygems.org) introduced an @_init instance variable guard in ERB#result and ERB#run to prevent code execution when an ERB object is reconstructed via Marshal.load (deserialization). However, three other public methods that also evaluate @src via eval() were not given the same guard: ERB#def_method, ERB#def_module, and ERB#def_class. An attacker who can trigger Marshal.load on untrusted data in a Ruby application that has erb loaded can use ERB#def_module (zero-arg, default parameters) as a code execution sink, bypassing the @_init protection entirely. ERB 4.0.3.1, 4.0.4.1, 6.0.1.1, and 6.0.4 patch the issue.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
65%
KEV
Not listed

Published

April 24, 2026

Last Modified

August 24, 2026

Advisory Details (1)

Auto-updated Apr 29, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

ERB @_init deserialization guard bypass via def_module / def_method / def_class · Advisory · ruby/erb · GitHub

https://github.com/ruby/erb/security/advisories/GHSA-q339-8rmv-2mhv

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatruby:3.3-9060020260630075016.92026-07-09redhat
redhatruby-0:3.0.4-161.el9_2.32026-07-06redhat
redhatruby-0:3.0.7-165.el9_6.12026-06-30redhat
redhatruby-0:3.3.10-11.el10_0.12026-06-30redhat
redhatruby:3.3-9040020260520083544.92026-06-17redhat
redhatruby-0:3.0.7-162.el9_4.22026-06-16redhat
redhatruby-0:3.0.4-160.2.el9_02026-05-26redhat
redhatruby4.0-0:4.0.3-34.el10_22026-05-26redhat
redhatruby:3.3-8100020260428163940.489197e62026-05-26redhat
redhatruby:4.0-9080020260513131334.92026-05-26redhat
redhatruby-0:3.3.10-12.el10_12026-05-18redhat
redhatruby-0:3.0.7-166.el9_72026-05-18redhat
redhatruby:3.3-9070020260428163621.92026-05-18redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
ruby2.72.7.4-1 ... 2.7.4-1+deb11u5 (6 versions)2.7.4-1+deb11u6
Debian:12(1)
PackageVulnerable rangeFixed inDependents
ruby3.13.1.2-7 ... 3.1.2-8.5 (8 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
ruby3.33.3.8-2, 3.3.8-2.1, 3.3.8-2.2
Debian:14(1)
PackageVulnerable rangeFixed inDependents
ruby3.33.3.8-2, 3.3.8-2.1, 3.3.8-2.2
RubyGems(1)
PackageVulnerable rangeFixed inDependents
erb6.0.2, 6.0.36.0.4

Weakness Classification(2)

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

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 208 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 19:31 UTCEPSS rescore
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-12 08:23 UTCOSV refresh
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 09:37 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 13:53 UTCEPSS rescore
  17. 2026-09-01 04:39 UTCEPSS rescore
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 14:46 UTCEPSS rescore
  23. 2026-08-25 13:49 UTCEPSS rescore
  24. 2026-08-24 13:31 UTCEG score recompute
  25. 2026-08-24 13:31 UTCVendor advisory
Show 75 more
  1. 2026-08-24 12:26 UTCEG score recompute
  2. 2026-08-24 12:26 UTCVendor advisory
  3. 2026-08-23 00:19 UTCEPSS rescore
  4. 2026-08-21 23:49 UTCEPSS rescore
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-17 14:54 UTCEG score recompute
  9. 2026-08-17 14:54 UTCVendor advisory
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-16 05:50 UTCEG score recompute
  13. 2026-08-16 05:50 UTCVendor advisory
  14. 2026-08-16 02:14 UTCEPSS rescore
  15. 2026-08-15 01:30 UTCEPSS rescore
  16. 2026-08-14 15:33 UTCVendor advisory
  17. 2026-08-14 04:10 UTCEG score recompute
  18. 2026-08-14 04:10 UTCVendor advisory
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-13 08:33 UTCVendor advisory
  21. 2026-08-12 17:54 UTCEG score recompute
  22. 2026-08-12 17:54 UTCVendor advisory
  23. 2026-08-12 13:51 UTCEPSS rescore
  24. 2026-08-11 16:42 UTCEG score recompute
  25. 2026-08-11 16:42 UTCVendor advisory
  26. 2026-08-11 13:43 UTCEPSS rescore
  27. 2026-08-11 02:11 UTCEG score recompute
  28. 2026-08-11 02:11 UTCVendor advisory
  29. 2026-08-11 00:00 UTCEPSS rescore
  30. 2026-08-10 02:09 UTCVendor advisory
  31. 2026-08-09 14:46 UTCEG score recompute
  32. 2026-08-09 14:46 UTCVendor advisory
  33. 2026-08-09 13:46 UTCEPSS rescore
  34. 2026-08-09 03:22 UTCEG score recompute
  35. 2026-08-09 03:22 UTCVendor advisory
  36. 2026-08-08 16:37 UTCEPSS rescore
  37. 2026-08-08 11:24 UTCVendor advisory
  38. 2026-08-08 00:01 UTCEG score recompute
  39. 2026-08-08 00:01 UTCVendor advisory
  40. 2026-08-07 12:38 UTCEG score recompute
  41. 2026-08-07 12:38 UTCVendor advisory
  42. 2026-08-06 13:46 UTCEPSS rescore
  43. 2026-08-06 12:38 UTCVendor advisory
  44. 2026-08-06 01:15 UTCEG score recompute
  45. 2026-08-06 01:15 UTCVendor advisory
  46. 2026-08-05 19:17 UTCEPSS rescore
  47. 2026-08-05 13:52 UTCEG score recompute
  48. 2026-08-05 13:52 UTCVendor advisory
  49. 2026-08-05 12:39 UTCEG score recompute
  50. 2026-08-05 12:39 UTCVendor advisory
  51. 2026-08-04 15:10 UTCEPSS rescore
  52. 2026-08-04 10:38 UTCEPSS rescore
  53. 2026-08-03 21:07 UTCEG score recompute
  54. 2026-08-03 21:07 UTCVendor advisory
  55. 2026-08-03 10:36 UTCEPSS rescore
  56. 2026-08-02 22:50 UTCVendor advisory
  57. 2026-08-02 11:27 UTCEG score recompute
  58. 2026-08-02 11:27 UTCVendor advisory
  59. 2026-08-02 02:27 UTCEPSS rescore
  60. 2026-08-01 04:16 UTCEPSS rescore
  61. 2026-07-30 16:28 UTCEPSS rescore
  62. 2026-07-30 01:30 UTCEPSS rescore
  63. 2026-07-28 15:36 UTCEPSS rescore
  64. 2026-07-27 14:13 UTCEPSS rescore
  65. 2026-07-26 14:54 UTCEPSS rescore
  66. 2026-07-26 14:54 UTCEPSS rescore
  67. 2026-07-25 14:18 UTCEPSS rescore
  68. 2026-07-24 14:17 UTCEPSS rescore
  69. 2026-07-23 14:18 UTCEPSS rescore
  70. 2026-07-23 03:11 UTCEG score recompute
  71. 2026-07-22 14:08 UTCEPSS rescore
  72. 2026-07-21 15:24 UTCEPSS rescore
  73. 2026-07-20 17:08 UTCEPSS rescore
  74. 2026-07-20 14:02 UTCOSV refresh
  75. 2026-07-19 14:31 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-41316?
CVE-2026-41316 is a high vulnerability published on April 24, 2026. ERB is a templating system for Ruby. Ruby 2.7.0 (before ERB 2.2.0 was published on rubygems.org) introduced an @init instance variable guard in ERB#result and ERB#run to prevent code execution when an ERB object is reconstructed via Marshal.load (deserialization). However, three other public…
When was CVE-2026-41316 disclosed?
CVE-2026-41316 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on August 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41316 actively exploited?
CVE-2026-41316 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 35.1% of all scored CVEs.
What is the CVSS score of CVE-2026-41316?
CVE-2026-41316 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-41316?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41316, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41316

Explore →

Is Your Infrastructure Affected by CVE-2026-41316?

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