Summary
Active Support: Possible DoS vulnerability in Active Support safe_constantize
Details
The check that decides whether safe_constantize returns nil or re-raises the LoadError now matches the first segment of the constant name against the error message as a literal string, and no longer compiles a regular expression. It returns the same result as before for constant names that contain no regular expression syntax.
Affected applications
An application is affected if it meets all of these requirements:
- Mounts Action Cable, which a new Rails application does by default at
/cable(config.action_cable.mount_path), or otherwise passes untrusted input tosafe_constantize. - Accepts Action Cable connections from untrusted clients.
ApplicationCable::Connection#connectauthenticates nobody unless the application adds a check.
Workarounds
Applications that do not use Action Cable can set config.action_cable.mount_path = nil to remove the endpoint. Applications that use Action Cable can call reject_unauthorized_connection in ApplicationCable::Connection#connect for unauthenticated clients, which limits exposure to authenticated users but does not remove it.
Releases
The fixed releases are available at the normal locations.
Patches for those who cannot upgrade at once:
- 8.1: https://github.com/rails/rails/commit/95aa9e416016524956d4904fed96eaed079580bb.patch
- 8.0: https://github.com/rails/rails/commit/210ac22d446c8e2625b091e79256806b836eee20.patch
Versions affected
- activesupport < 8.0.5.2
- activesupport >= 8.1, < 8.1.4.1
Credit
This issue was responsibly reported by Felix Tscheulin (flixt) through HackerOne researcher scheja, and independently by Bucky Wolfe (Igneous), who provided a proof of concept that crashes the server. It was also found by the Anthropic OSS Scanner (ANT-2026-ZUN5KU3Q).
Impact
When constant lookup raises LoadError, ActiveSupport::Inflector#safe_constantize (and String#safe_constantize) builds a regular expression from the requested constant name without escaping it, so a caller that passes untrusted input lets the attacker choose the source of a pattern that the application compiles. Crafted patterns can trigger defects in Ruby's regular expression compiler, possibly leading to a crash of the server process, and repeated requests could keep the application unavailable.
Action Cable passes the channel value of each subscribe command to safe_constantize before any channel lookup, so in the default configuration an unauthenticated client of the Action Cable endpoint can reach this code.
CVE-2026-126080 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (8.1.4.1, 8.0.5.2); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
activesupport to 8.1.4.1 or later; activesupport to 8.0.5.2 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-126080? CVE-2026-126080 is a high-severity security vulnerability in activesupport (rubygems), affecting versions >= 8.1.0.beta1, < 8.1.4.1. It is fixed in 8.1.4.1, 8.0.5.2.
- How severe is CVE-2026-126080? CVE-2026-126080 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of activesupport are affected by CVE-2026-126080? activesupport (rubygems) versions >= 8.1.0.beta1, < 8.1.4.1 is affected.
- Is there a fix for CVE-2026-126080? Yes. CVE-2026-126080 is fixed in 8.1.4.1, 8.0.5.2. Upgrade to this version or later.
- Is CVE-2026-126080 exploitable, and should I be worried? Whether CVE-2026-126080 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-126080 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-126080?
- Upgrade
activesupportto 8.1.4.1 or later - Upgrade
activesupportto 8.0.5.2 or later
- Upgrade