| CVE ID | Severity | Package | Affected Version | Fixed Version | CVSS Score | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CVE-2026-41316 | high | pkg:gem/erb@4.0.4 | =4.0.4 | 4.0.4.1 | 8.1 | |||||||||||||||||||||
SummaryRuby 2.7.0 (before ERB 2.2.0 was published on rubygems.org) introduced an
An attacker who can trigger The @_init GuardIn
In
When an ERB object is reconstructed via The Bypass
Method wrapper breakout
Proof of ConceptMinimal (ERB only)
Marshal deserialization (ERB + ActiveSupport)When combined with
Chain:
Verified on: Ruby 3.3.8 / RubyGems 3.6.7 / ActiveSupport 7.2.3 / ERB 6.0.1 ImpactScopeAny Ruby application that calls
Severity justificationThe This bypass renders the @_init mitigation ineffective across all ERB versions from 2.2.0 through 6.0.3 (latest as of April 2026). Combined with the DeprecatedInstanceVariableProxy gadget (present in all ActiveSupport versions through 7.2.3), this constitutes a universal RCE gadget chain for Ruby 3.2+ applications using Rails. Gadget chain historySix generations of Ruby Marshal gadget chains have been discovered (2018-2026). Each bypassed the previous round of mitigations:
PatchesThe problem has been patched at the following ERB versions. Please upgrade your erb.gem to any one of them.
Add the
Package URL(s):
More Info (NVD): | ||||||||||||||||||||||||||
| CVE-2026-5435 | high | glibc | >0 | not fixed | 7.3 | |||||||||||||||||||||
| CVE-2026-6238 | medium | glibc | >0 | not fixed | 6.5 | |||||||||||||||||||||
| CVE-2025-45582 | medium | tar | >=1.35+dfsg-3.1 | not fixed | 4.1 | |||||||||||||||||||||
| CVE-2024-3205 | unspecified | libyaml | >=0.2.5-1 | not fixed | 3.1 | |||||||||||||||||||||
| CVE-2024-35329 | unspecified | libyaml | >=0.2.5-1 | not fixed | 3.1 | |||||||||||||||||||||
| CVE-2005-2541 | low | tar | >0 | not fixed | 3.1 | |||||||||||||||||||||
| CVE-2007-5686 | low | shadow | >0 | not fixed | 3.1 | |||||||||||||||||||||
| CVE-2010-0928 | low | openssl | >=3.2.1-3 | not fixed | 3.1 | |||||||||||||||||||||
| CVE-2010-4756 | low | glibc | >0 | not fixed | 3.1 | |||||||||||||||||||||
Exploitation could lead to severe consequences, such as system compromise or data loss. Requires immediate attention.
Vulnerability could be exploited relatively easily and lead to significant impact. Requires prompt attention.
Exploitation is possible but might require specific conditions. Impact is moderate. Should be addressed in a timely manner.
Exploitation is difficult or impact is minimal. Address when convenient or as part of regular maintenance.
Severity is not determined, informational, or negligible. Review based on context.
Sliplane is a simple container hosting solution. It enables you to deploy your containers in the cloud within minutes and scale up as you grow.
CVE stands for Common Vulnerabilities and Exposures. It is a standardized identifier for known security vulnerabilities, allowing developers and organizations to track and address potential risks effectively. For more information, visit cve.mitre.org.
The CVE Scanner is a powerful tool that helps you identify known vulnerabilities in your Docker images. By scanning your images against a comprehensive database of Common Vulnerabilities and Exposures (CVEs), you can ensure that your applications are secure and up-to-date. For more details, checkout the NIST CVE Database.
The CVE Scanner analyzes your Docker images against a comprehensive database of known vulnerabilities. It uses Docker Scout under the hood to provide detailed insights into affected packages, severity levels, and available fixes, empowering you to take immediate action.
With the rise of supply chain attacks, ensuring the security of your applications has become more critical than ever. CVE scanning plays a vital role in identifying vulnerabilities that could be exploited by attackers, especially those introduced through dependencies and third-party components. Regularly scanning and securing your Docker images is essential to protect your applications from these evolving threats.
Patching your Docker images is a critical step in maintaining the security and stability of your applications. By regularly updating your images to include the latest security patches, you can address known vulnerabilities and reduce the risk of exploitation. This proactive approach ensures that your applications remain resilient against emerging threats and helps maintain compliance with security best practices.
Try out Sliplane - a simple Docker hosting solution. It provides you with the tools to deploy, manage and scale your containerized applications.