Advisory

GHSA-3w5p-95mh-gq75

Also known as: CVE-2026-55254

Summary

NCalc: Denial of Service via Unbounded and Non-Terminating Factorial Evaluation

Details

Impact

A denial-of-service (DoS) vulnerability exists in the factorial operator implementation of NCalc. Specially crafted expressions containing extremely large factorial operands can trigger excessive CPU consumption or cause evaluation to enter a non-terminating loop due to integer overflow in the factorial calculation logic.

Applications that evaluate untrusted expressions using affected versions of NCalc may be vulnerable to resource exhaustion, potentially resulting in service disruption or application unresponsiveness.

This issue can be triggered with expressions such as:

99999999999999!
9223372036854775807!
1.5e16!

Patches

The vulnerability has been fixed by adding bounds validation for factorial operands and rejecting unsupported values before evaluation.

Users should upgrade to the first release containing the fix from pull request #575. (v6.1.1+)

Workarounds

If upgrading is not immediately possible:

  • Do not evaluate expressions originating from untrusted users.
  • Validate or sanitize expressions before evaluation and reject factorial operations on large values.
  • Implement execution time limits, request timeouts, or cancellation mechanisms around expression evaluation.

These mitigations may reduce exposure but do not fully address the underlying vulnerability.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-06-18 13:05 UTC
Modified
2026-06-18 13:26 UTC

Affected packages and fixes

NCalc.Core

NuGet · All systems

Affected

  • introduced 0, fixed 6.1.1 (ecosystem)

Fixed versions

6.1.1

Fix

The export has no generic command for this ecosystem.

NCalcSync

NuGet · All systems

Affected

  • introduced 0, fixed 6.1.1 (ecosystem)

Fixed versions

6.1.1

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences