4.8
Medium
NCalc.Core

CVE-2026-55254

CVE-2026-55254 is a medium-severity integer overflow or wraparound vulnerability in NCalc.Core (nuget), affecting versions < 6.1.1. It is fixed in 6.1.1.

Key facts
CVSS score
4.8
Medium
Attack vector
Adjacent
Issuing authority
GitHub Advisory Database
Affected package
NCalc.Core
Fixed in
6.1.1
Disclosed
2026

Summary

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: 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.

Impact

What is integer overflow or wraparound?

An arithmetic operation produces a value that exceeds the integer type's maximum, causing it to wrap to an unexpected small value. Typical impact: incorrect size calculations leading to heap overflows or logic errors.

Severity and exposure

CVE-2026-55254 has a CVSS score of 4.8 (Medium). The vector is reachable from an adjacent network, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (6.1.1). Upgrading removes the vulnerable code path.

Affected versions

nuget

  • NCalc.Core (< 6.1.1)
  • NCalcSync (< 6.1.1)

Security releases

  • NCalc.Core → 6.1.1 (nuget)
  • NCalcSync → 6.1.1 (nuget)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-55254 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-55254 is reachable in your applications. Get a demo

Remediation advice

Upgrade the following packages to resolve this vulnerability:

  • Upgrade NCalc.Core to 6.1.1 or later
  • Upgrade NCalcSync to 6.1.1 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-55254

What is CVE-2026-55254?

CVE-2026-55254 is a medium-severity integer overflow or wraparound vulnerability in NCalc.Core (nuget), affecting versions < 6.1.1. It is fixed in 6.1.1. An arithmetic operation produces a value that exceeds the integer type's maximum, causing it to wrap to an unexpected small value.

How severe is CVE-2026-55254?

CVE-2026-55254 has a CVSS score of 4.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2026-55254?
  • NCalc.Core (nuget) (versions < 6.1.1)
  • NCalcSync (nuget) (versions < 6.1.1)
Is there a fix for CVE-2026-55254?

Yes. CVE-2026-55254 is fixed in 6.1.1. Upgrade to this version or later.

Is CVE-2026-55254 exploitable, and should I be worried?

Whether CVE-2026-55254 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-55254 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-55254?
  • Upgrade NCalc.Core to 6.1.1 or later
  • Upgrade NCalcSync to 6.1.1 or later

Stop the waste.
Protect your environment with Kodem.