CVE-2026-33176 | rails activesupport prior 7.2.3.1/8.0.4.1/8.1.2.1 resource consumption (GHSA-2j26-frm8-cmj9)

VDB-352641 · CVE-2026-33176 · GHSA-2J26-FRM8-CMJ9 RAILS ACTIVESUPPORT PRIOR 7.2.3.1/8.0.4.1/8.1.2.1 RESOURCE CONSUMPTION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.1 $0-$5k 1.16+ Summaryinfo A vulnerability identified as problematic has been detected in rails activesupport. This vulnerability affects unknown code. Performing a manipulation results in resource consumption. This vulnerability is identified as CVE-2026-33176. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component. Detailsinfo A vulnerability, which was classified as problematic, was found in rails activesupport. This affects some unknown functionality. The manipulation with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. This is going to have an impact on availability. The summary by CVE is: Active Support is a toolkit of support libraries and Ruby core extensions extracted from the Rails framework. Prior to versions 8.1.2.1, 8.0.4.1, and 7.2.3.1, Active Support number helpers accept strings containing scientific notation (e.g. `1e10000`), which `BigDecimal` expands into extremely large decimal representations. This can cause excessive memory allocation and CPU consumption when the expanded number is formatted, possibly resulting in a DoS vulnerability. Versions 8.1.2.1, 8.0.4.1, and 7.2.3.1 contain a patch. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-33176 since 03/17/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue. Upgrading to version 7.2.3.1, 8.0.4.1 or 8.1.2.1 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 19dbab51ca086a657bb86458042bc44314916bcb is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. Productinfo Vendor rails Name activesupport License open-source CPE 2.3info 🔒 CPE 2.2info 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 5.3 VulDB Meta Temp Score: 5.1 VulDB Base Score: 5.3 VulDB Temp Score: 5.1 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Resource consumption CWE: CWE-400 / CWE-404 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: activesupport 7.2.3.1/8.0.4.1/8.1.2.1 Patch: 19dbab51ca086a657bb86458042bc44314916bcb Timelineinfo 03/17/2026 CVE reserved 03/24/2026 +7 days Advisory disclosed 03/24/2026 +0 days VulDB entry created 03/24/2026 +0 days VulDB entry last update Sourcesinfo Advisory: GHSA-2j26-frm8-cmj9 Status: Confirmed CVE: CVE-2026-33176 (🔒) GCVE (CVE): GCVE-0-2026-33176 GCVE (VulDB): GCVE-100-352641 Entryinfo Created: 03/24/2026 02:53 Changes: 03/24/2026 02:53 (70) Complete: 🔍 Cache ID: 99:1D5:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸