ACTIVESUPPORT · GHSA-8474-xrp6-wh69 · Package
FIX → 8.1.4.1 +1
ActiveSupport's safe_constantize builds a regular expression from an unescaped constant name, so untrusted input can supply a crafted pattern. Crafted patterns can crash the server process, and repeated requests can keep the application unavailable.
first public Nov 4, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Applications that mount Action Cable, which a new Rails application does by default at /cable, or that pass untrusted input to safe_constantize are exposed. Action Cable connections from untrusted clients are the main path, since the default connect method authenticates nobody unless the application adds a check. Applications that do not use Action Cable and do not pass untrusted input to safe_constantize can skip it.
Not affected if auth-required, no-action-cable, untrusted-input-never-reaches-safe-constantize
Who cares action-cable, activesupport, rails, ruby
bundle exec gem list activesupport and compare it to the fixed versions./cable (config.action_cable.mount_path) and for subscribe commands reaching safe_constantize.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.
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.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
ApplicationCable::Connection#connect rejects unauthenticated clients.Upgrade to 8.1.4.1 +1
8.1.4.1 for the 8.1 line8.0.5.2 for the 8.0 lineAn application is affected if it meets all of these requirements:
/cable (config.action_cable.mount_path), or otherwise passes untrusted input to safe_constantize.ApplicationCable::Connection#connect authenticates nobody unless the application adds a check.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.
The fixed releases are available at the normal locations.
Patches for those who cannot upgrade at once:
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).