Is activesupport 5.2 vulnerable?
RubyGems · 22 releases from 5.2.0 to 5.2.8.1 · latest activesupport is 8.1.4.1 · checked 18 Nov 2026
Yes: 7 known advisories
Yes. activesupport 5.2.8.1, the last 5.2 release, is affected by 7 known security advisories (1 high, 5 medium, 1 low), including CVE-2026-126080, CVE-2026-33176, CVE-2026-33170. 1 more affects earlier 5.2.x releases. Upgrade to 8.0.5.2 or later to fix all of them.
bundle update --conservative activesupport # Gemfile: '>= 8.0.5.2'Is your project on an affected activesupport?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting activesupport 5.2.8.1
Active Support: Possible DoS vulnerability in Active Support safe_constantize
- Affected
- >=8.1.0.beta1 <8.1.4.1 · <8.0.5.2
- Fixed in
- 8.0.5.2, 8.1.4.1
Rails Active Support has a possible DoS vulnerability in its number helpers
- Affected
- >=8.1.0.beta1 <8.1.2.1 · >=8.0.0.beta1 <8.0.4.1 · <7.2.3.1
- Fixed in
- 7.2.3.1, 8.0.4.1, 8.1.2.1
Rails Active Support has a possible XSS vulnerability in SafeBuffer#%
- Affected
- >=8.1.0.beta1 <8.1.2.1 · >=8.0.0.beta1 <8.0.4.1 · <7.2.3.1
- Fixed in
- 7.2.3.1, 8.0.4.1, 8.1.2.1
Rails Active Support has a possible ReDoS vulnerability in number_to_delimited
- Affected
- >=8.1.0.beta1 <8.1.2.1 · >=8.0.0.beta1 <8.0.4.1 · <7.2.3.1
- Fixed in
- 7.2.3.1, 8.0.4.1, 8.1.2.1
Active Support Possibly Discloses Locally Encrypted Files
- Affected
- >=5.2.0 <6.1.7.5 · >=7.0.0 <7.0.7.1
- Fixed in
- 6.1.7.5, 7.0.7.1
Possible XSS Security Vulnerability in SafeBuffer#bytesplice
- Affected
- >=7.0.0 <7.0.4.3 · <6.1.7.3
- Fixed in
- 6.1.7.3, 7.0.4.3
ReDoS based DoS vulnerability in Active Support's underscore
- Affected
- <6.1.7.1 · >=7.0.0 <7.0.4.1
- Fixed in
- 6.1.7.1, 7.0.4.1
Fixed within 5.2.x, affecting earlier releases
ActiveSupport potentially unintended unmarshalling of user-provided objects in MemCacheStore and RedisCacheStore
- Affected
- >=5.0.0 <5.2.4.3 · >=6.0.0 <6.0.3.1
- Fixed in
- 5.2.4.3, 6.0.3.1
Every activesupport 5.2.x release
Affected: 5.2.0 to 5.2.8.1. Latest activesupport: 8.1.4.1.
| Version | Known advisories |
|---|---|
| activesupport 5.2.8.1 | CVE-2026-126080, CVE-2026-33176, CVE-2026-33170, CVE-2026-33169, CVE-2023-38037, CVE-2023-28120, CVE-2023-22796 |
| activesupport 5.2.8 | CVE-2026-126080, CVE-2026-33176, CVE-2026-33170, CVE-2026-33169, CVE-2023-38037, CVE-2023-28120, CVE-2023-22796 |
| activesupport 5.2.7.1 | CVE-2026-126080, CVE-2026-33176, CVE-2026-33170, CVE-2026-33169, CVE-2023-38037, CVE-2023-28120, CVE-2023-22796 |
| activesupport 5.2.7 | CVE-2026-126080, CVE-2026-33176, CVE-2026-33170, CVE-2026-33169, CVE-2023-38037, CVE-2023-28120, CVE-2023-22796 |
| activesupport 5.2.6.3 | CVE-2026-126080, CVE-2026-33176, CVE-2026-33170, CVE-2026-33169, CVE-2023-38037, CVE-2023-28120, CVE-2023-22796 |
| activesupport 5.2.6.2 | CVE-2026-126080, CVE-2026-33176, CVE-2026-33170, CVE-2026-33169, CVE-2023-38037, CVE-2023-28120, CVE-2023-22796 |
| activesupport 5.2.6.1 | CVE-2026-126080, CVE-2026-33176, CVE-2026-33170, CVE-2026-33169, CVE-2023-38037, CVE-2023-28120, CVE-2023-22796 |
| activesupport 5.2.6 | CVE-2026-126080, CVE-2026-33176, CVE-2026-33170, CVE-2026-33169, CVE-2023-38037, CVE-2023-28120, CVE-2023-22796 |
| activesupport 5.2.5 | CVE-2026-126080, CVE-2026-33176, CVE-2026-33170, CVE-2026-33169, CVE-2023-38037, CVE-2023-28120, CVE-2023-22796 |
| activesupport 5.2.4.6 | CVE-2026-126080, CVE-2026-33176, CVE-2026-33170, CVE-2026-33169, CVE-2023-38037, CVE-2023-28120, CVE-2023-22796 |
| activesupport 5.2.4.5 | CVE-2026-126080, CVE-2026-33176, CVE-2026-33170, CVE-2026-33169, CVE-2023-38037, CVE-2023-28120, CVE-2023-22796 |
| activesupport 5.2.4.4 | CVE-2026-126080, CVE-2026-33176, CVE-2026-33170, CVE-2026-33169, CVE-2023-38037, CVE-2023-28120, CVE-2023-22796 |
| activesupport 5.2.4.3 | CVE-2026-126080, CVE-2026-33176, CVE-2026-33170, CVE-2026-33169, CVE-2023-38037, CVE-2023-28120, CVE-2023-22796 |
| activesupport 5.2.4.2 | CVE-2026-126080, CVE-2026-33176, CVE-2026-33170, CVE-2026-33169, CVE-2023-38037, CVE-2023-28120, CVE-2023-22796, CVE-2020-8165 |
| activesupport 5.2.4.1 | CVE-2026-126080, CVE-2026-33176, CVE-2026-33170, CVE-2026-33169, CVE-2023-38037, CVE-2023-28120, CVE-2023-22796, CVE-2020-8165 |
| activesupport 5.2.4 | CVE-2026-126080, CVE-2026-33176, CVE-2026-33170, CVE-2026-33169, CVE-2023-38037, CVE-2023-28120, CVE-2023-22796, CVE-2020-8165 |
| activesupport 5.2.3 | CVE-2026-126080, CVE-2026-33176, CVE-2026-33170, CVE-2026-33169, CVE-2023-38037, CVE-2023-28120, CVE-2023-22796, CVE-2020-8165 |
| activesupport 5.2.2.1 | CVE-2026-126080, CVE-2026-33176, CVE-2026-33170, CVE-2026-33169, CVE-2023-38037, CVE-2023-28120, CVE-2023-22796, CVE-2020-8165 |
| activesupport 5.2.2 | CVE-2026-126080, CVE-2026-33176, CVE-2026-33170, CVE-2026-33169, CVE-2023-38037, CVE-2023-28120, CVE-2023-22796, CVE-2020-8165 |
| activesupport 5.2.1.1 | CVE-2026-126080, CVE-2026-33176, CVE-2026-33170, CVE-2026-33169, CVE-2023-38037, CVE-2023-28120, CVE-2023-22796, CVE-2020-8165 |
| activesupport 5.2.1 | CVE-2026-126080, CVE-2026-33176, CVE-2026-33170, CVE-2026-33169, CVE-2023-38037, CVE-2023-28120, CVE-2023-22796, CVE-2020-8165 |
| activesupport 5.2.0 | CVE-2026-126080, CVE-2026-33176, CVE-2026-33170, CVE-2026-33169, CVE-2023-38037, CVE-2023-28120, CVE-2023-22796, CVE-2020-8165 |
Which of your client projects are still on activesupport 5.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact activesupport version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other activesupport versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.