Vulnerability in decimal (CVE-2026-32686)
Summary
Vulnerability in decimal (CVE-2026-32686). Risk of unauthorized operations or information disclosure. Exploitable via decimal. Mitigation: upgrade to 3.0.0 or later.
Original description
The description as published by the source.
Summary
Uncontrolled Resource Consumption vulnerability in ericmj decimal allows unauthenticated remote Denial of Service.
The decimal library does not bound the exponent on parsed input. Storing a decimal with a very large exponent (e.g. Decimal.new("1e1000000000")) is accepted without error. Subsequent calls to arithmetic functions (Decimal.add/2, Decimal.sub/2, Decimal.div/2M), Decimal.to_string/2M with :normalM or :xsdM format, Decimal.to_integer/1M, Decimal.round/3M, or Decimal.compare/3M with a threshold allocate memory proportional to the exponent value, which can exhaust available memory and crash the BEAM VM.
Any application that accepts user-supplied decimal input and subsequently performs arithmetic, rounding, conversion to integer, or string formatting on it is exposed. A single malicious request is sufficient to cause an out-of-memory crash.
This issue affects decimal: from 0.1.0 before 3.0.0.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-32686 has been found in decimal.
Attackers can target a specific entry point like decimal over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade decimal to 3.0.0 or later.
If unsure, ask your IT team or search "decimal CVE-2026-32686" on the vendor's site.
CVE-2026-32686 (decimal) — CWE-400
Attack surface: decimal / exp / add_align / String.Chars
Patched: 3.0.0 — 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.
A vulnerability (CWE-400) exists in decimal. Attackers reach the vulnerable code path via decimal.
Check the vendor advisory for the affected versions of decimal. Attack surface: decimal / exp / add_align / String.Chars.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.0.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'decimal' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'decimal' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
decimalを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade decimal to 3.0.0ステージング環境で 3.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- package hex.pm
- patch github.com
- web cna.erlef.org
- web osv.dev
- web github.com
- web github.com
- web github.com
- web github.com