VulertSecurity VulertSecurity

Vulnerability Database · Hex · Package report

decimal: vulnerability history, versions and safety

decimal is a package in the Hex ecosystem. Vulert records 3 vulnerabilities for it across 36 releases, from May 2026 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded M1 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 10 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all decimal vulnerabilities

Vulert verdict on decimal 3.2.0 i

Updated on 23 Oct 2026

Good news: 3.2.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 92/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Not enough data

What to do: Stay on 3.2.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.2.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 3.2.0 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 3 in the last year i
  • Latest disclosure 10 Oct 2026 i
  • Highest CVSS 6.9 i
  • With no published fix 0 i
  • Depended on by 163,594,467 packages i
  • Last release this month i

Version list, release dates, licence and dependants published by hex.pm, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for decimal, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.2.0 10 Oct 2026 none — — Details →
3.1.2 10 Oct 2026 none — — Details →
3.1.1 27 May 2026 U1 — Yes Details →
3.1.0 08 May 2026 U1 — Yes Details →
3.0.0 07 May 2026 U1 — Yes Details →
2.4.1 08 May 2026 M1 U1 — Yes Details →
2.4.0 07 May 2026 M1 U2 — Yes Details →
2.3.0 13 Dec 2024 M1 U2 — Yes Details →
2.2.0 13 Nov 2024 M1 U2 — Yes Details →
2.1.1 26 Apr 2023 M1 U2 — Yes Details →
2.1.0 26 Apr 2023 M1 U2 — Yes Details →
2.0.0 08 Sep 2020 M1 U2 — Yes Details →
2.0.0-rc.0 21 Jan 2020 M1 U2 — Yes Details →
1.9.0 08 Sep 2020 M1 U2 — Yes Details →
1.9.0-rc.0 07 Jan 2020 M1 U2 — Yes Details →
1.8.1 20 Dec 2019 M1 U2 — Yes Details →
1.8.0 24 Jun 2019 M1 U2 — Yes Details →
1.7.0 16 Feb 2019 M1 U2 — Yes Details →
1.6.0 22 Nov 2018 M1 U2 — Yes Details →
1.5.0 24 Mar 2018 M1 U2 — Yes Details →
1.4.1 12 Oct 2017 M1 U2 — Yes Details →
1.4.0 25 Jun 2017 M1 U2 — Yes Details →
1.3.1 11 Nov 2016 M1 U2 — Yes Details →
1.3.0 10 Nov 2016 M1 U2 — Yes Details →
1.2.0 26 Sep 2016 M1 U2 — Yes Details →
1.1.2 24 Apr 2016 M1 U2 — Yes Details →
1.1.1 26 Dec 2015 M1 U2 — Yes Details →
1.1.0 31 Dec 2014 M1 U2 — Yes Details →
1.0.1 16 Dec 2014 M1 U2 — Yes Details →
1.0.0 09 Dec 2014 M1 U2 — Yes Details →
0.2.5 09 Sep 2014 M1 U2 — Yes Details →
0.2.4 03 Aug 2014 M1 U2 — Yes Details →
0.2.3 13 Jul 2014 M1 U2 — Yes Details →
0.2.2 18 Jun 2014 M1 U2 — Yes Details →
0.2.1 24 May 2014 M1 U2 — Yes Details →
0.2.0 01 May 2014 M1 U2 — Yes Details →
0.1.2 21 Apr 2014 M1 U2 — Yes Details →
0.1.1 21 Apr 2014 M1 U2 — Yes Details →

All 38 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for decimal

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-32686: Unbounded Exponent in Decimal Library Leads to Unauthenticated DoS 6.9 medium 3.0.0 07 May 2026
CVE-2026-32686: Decimal Package Unbounded Exponent Vulnerability Leading to DoS 6.9 medium 3.0.0 12 May 2026
CVE-2026-97853: Decimal Package Unbounded Allocation Vulnerability Leading to Denial of Service 6.9 medium 3.1.2 10 Oct 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About decimal

Is decimal safe to use?

Vulert records 3 vulnerabilities for decimal in Hex: 0 critical, 0 high, 1 medium and 0 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is decimal's Vulert package health score?

Vulert scores decimal 92/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of decimal affected?

No. 3.2.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does decimal have?

3 vulnerabilities are recorded for decimal in the Hex ecosystem: 0 critical, 0 high, 1 medium and 0 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new decimal vulnerabilities disclosed?

3 vulnerabilities were recorded for decimal in the last 12 months, and the oldest entry in this database dates to 07 May 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of decimal are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor decimal for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the decimal version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.