← Back
CVE-2026-33169
Vulnerability in activesupport (CVE-2026-33169)
Summary
vulnerability in activesupport (CVE-2026-33169). Risk of unauthorized operations or information disclosure. Exploitable via ``NumberToDelimitedConverter``. Mitigation: upgrade to `7.2.3.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-33169** has been found in activesupport.
Attackers can target a specific entry point like ``NumberToDelimitedConverter`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade activesupport to **7.2.3.1** or later.
If unsure, ask your IT team or search "activesupport CVE-2026-33169" on the vendor's site.
CVE-2026-33169 (activesupport) — CWE-400 /
Attack surface: `NumberToDelimitedConverter`
Patched: `7.2.3.1` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-400) exists in activesupport. Attackers reach the vulnerable code path via ``NumberToDelimitedConverter`` without authentication.
📍 Affected scope
activesupport — . Attack surface: `NumberToDelimitedConverter`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **7.2.3.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'activesupport' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'activesupport' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `activesupport` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade activesupport to 7.2.3.1ステージング環境で 7.2.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
rubygems
activesupport
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.2.3.1"}]}]
References
- web https://github.com/rails/rails/security/advisories/GHSA-cg4j-q9v8-6v38
- web https://github.com/rails/rails/commit/29154f1097da13d48fdb3200760b3e3da66dcb11
- web https://github.com/rails/rails/commit/b54a4b373c6f042cab6ee2033246b1c9ecc38974
- web https://github.com/rails/rails/commit/ec1a0e215efd27a3b3911aae6df978a80f456a49
- web https://github.com/rails/rails/releases/tag/v7.2.3.1
- web https://github.com/rails/rails/releases/tag/v8.0.4.1
- web https://github.com/rails/rails/releases/tag/v8.1.2.1
- web https://nvd.nist.gov/vuln/detail/CVE-2026-33169
- web https://github.com/rubysec/ruby-advisory-db/blob/master/gems/activesupport/CVE-2026-33169.yml
- web https://github.com/advisories/GHSA-cg4j-q9v8-6v38