HighGHSA-wh98-p28r-vrc9CVE-2022-23633

Exposure of information in Action Pack

Published 11 Feb 2022 · Updated 4 Feb 2026

Is your project on an affected actionpack?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

actionpackRubyGems
Affected
>=5.0.0.0 <5.2.6.2
Fixed in
5.2.6.2
Update to the fixed version for your release line, for example:bundle update --conservative actionpack # Gemfile: '>= 5.2.6.2'
actionpackRubyGems
Affected
>=6.0.0.0 <6.0.4.6
Fixed in
6.0.4.6
Update to the fixed version for your release line, for example:bundle update --conservative actionpack # Gemfile: '>= 6.0.4.6'
actionpackRubyGems
Affected
>=6.1.0.0 <6.1.4.6
Fixed in
6.1.4.6
Update to the fixed version for your release line, for example:bundle update --conservative actionpack # Gemfile: '>= 6.1.4.6'
actionpackRubyGems
Affected
>=7.0.0.0 <7.0.2.2
Fixed in
7.0.2.2
Update to the fixed version for your release line, for example:bundle update --conservative actionpack # Gemfile: '>= 7.0.2.2'

Details

Impact

Under certain circumstances response bodies will not be closed, for example a bug in a webserver or a bug in a Rack middleware. In the event a response is *not* notified of a close, ActionDispatch::Executor will not know to reset thread local state for the next request. This can lead to data being leaked to subsequent requests, especially when interacting with ActiveSupport::CurrentAttributes.

Upgrading to the FIXED versions of Rails will ensure mitigation of this issue even in the context of a buggy webserver or middleware implementation.

Patches

This has been fixed in Rails 7.0.2.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2.

Workarounds

Upgrading is highly recommended, but to work around this problem the following middleware can be used:

class GuardedExecutor < ActionDispatch::Executor
  def call(env)
    ensure_completed!
    super
  end

  private

    def ensure_completed!
      @executor.new.complete! if @executor.active?
    end
end

# Ensure the guard is inserted before ActionDispatch::Executor
Rails.application.configure do
  config.middleware.swap ActionDispatch::Executor, GuardedExecutor, executor
end

Is GHSA-wh98-p28r-vrc9 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected actionpack, and gives you the command that fixes it.

More advisories for actionpack

  • MediumCVE-2026-126072Action Pack: Possible DoS vulnerability in Action Controller Live streaming · 12 Nov 2026
  • MediumCVE-2026-126077Action Pack: Possible sensitive session information leak in Active Storage proxy mode · 12 Nov 2026
  • HighCVE-2026-126081Action Pack: Possible Strong Parameters Bypass in Parameters#each_key · 12 Nov 2026
  • MediumCVE-2026-126073Action Pack: Possible cache poisoning in Action Pack content negotiation · 10 Nov 2026
  • LowCVE-2026-126067Action Pack: Missing SameSite attribute on session cookies from Action Pack session stores · 10 Nov 2026
  • HighCVE-2026-126083Action Pack: Possible IP spoofing in Action Dispatch RemoteIp · 10 Nov 2026
All 69 advisories for actionpack

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.