Vulnerabilities

Vulnerability · HSEC-2023-0007

readFloat: memory exhaustion with large exponent

Published Nov 14, 2025 · catalog updated May 29, 2026 · readFloat: memory exhaustion with

Open the advisory

Exploitation likelihood is not on this record for HSEC-2023-0007. A missing EPSS score is not a low risk. Compare readFloat: memory exhaustion with with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (readFloat: memory exhaustion with).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Unknown—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Not established
Affected products
Hackage base · Hackage toml-reader

# : memory exhaustion with large exponent takes time and memory linear in the size of the number _denoted_ by the input string. In particular, processing a number expressed in scientific notation with a very large exponent could cause a denial of service. The slowdown is observable on a modern machine running GHC 9.4.4: ## In *base* is defined for all : The type class does not express any bounds on the size of values representable in the types for which instances exist, so bounds checking is not possible (in this *generic* function). uses to which, among other things, calculates , which seems to take linear time and memory. **Mitigation:** use . The instances for and perform bounds checks on the exponent, via . ## In *toml-reader* The issue was detected in *toml-reader* version 0.1.0.0, and mitigated in version 0.2.0.0 by immediately returning when the exponent is large enough that there's no reason to process it.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Hackage base3.0.3.1, 3.0.3.2, 4.0.0.0
  • Hackage basefrom 3.0.3.1
  • Hackage toml-reader0.1.0.0 → 0.2.0.0

How to fix HSEC-2023-0007

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for HSEC-2023-0007. A missing EPSS score is not a low risk. Compare readFloat: memory exhaustion with with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 3.0.3.1, 3.0.3.2, 4.0.0.0, from 3.0.3.1, 0.1.0.0 → 0.2.0.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Nov 14, 2025 · OpenSSF OSV / OSV Scanner

    Detected

    # : memory exhaustion with large exponent takes time and memory linear in the size of the number _denoted_ by the input string. In particular, processing a number expressed in scientific notation with a very large exponent could cause a denial of service. The slowdown is observable on a modern machine running GHC 9.4.4: ## In *base* is defined for all : The type class does not express any bounds o

  2. May 29, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    toml-reader fixed in 0.2.0.0

  3. May 29, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    toml-reader fixed in 0.2.0.0

  4. May 29, 2026 · OpenSSF OSV / OSV Scanner

    Updated

    # : memory exhaustion with large exponent takes time and memory linear in the size of the number _denoted_ by the input string. In particular, processing a number expressed in scientific notation with a very large exponent could cause a denial of service. The slowdown is observable on a modern machine running GHC 9.4.4: ## In *base* is defined for all : The type class does not express any bounds o

Sources

References

Freshness

Last verified in this catalog May 29, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.