What is CVE-2024-41655?

CVE-2024-41655 is a high-severity inefficient regular expression (ReDoS) vulnerability in tf2-item-format (npm), affecting versions >= 4.2.6, <= 5.9.13. It is fixed in 5.9.14. A regular expression with worst-case exponential or polynomial matching time is applied to untrusted input, causing excessive CPU use.

How severe is CVE-2024-41655?

CVE-2024-41655 has a CVSS score of 7.5 (High). 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 versions of tf2-item-format are affected by CVE-2024-41655?

tf2-item-format (npm) versions >= 4.2.6, <= 5.9.13 is affected.

Is there a fix for CVE-2024-41655?

Yes. CVE-2024-41655 is fixed in 5.9.14. Upgrade to this version or later.

Is CVE-2024-41655 exploitable, and should I be worried?

Whether CVE-2024-41655 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.

What actually determines whether CVE-2024-41655 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.

CVE-2024-41655 in tf2-item-format

Q: How severe is CVE-2024-41655?

CVE-2024-41655 has a CVSS score of 7.5 (High). 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.

Q: Which versions of tf2-item-format are affected by CVE-2024-41655?

tf2-item-format (npm) versions >= 4.2.6, <= 5.9.13 is affected.

Q: Is there a fix for CVE-2024-41655?

Yes. CVE-2024-41655 is fixed in 5.9.14. Upgrade to this version or later.

Q: Is CVE-2024-41655 exploitable, and should I be worried?

Whether CVE-2024-41655 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.

Q: What actually determines whether CVE-2024-41655 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.

Q: How do I fix CVE-2024-41655?

Upgrade tf2-item-format to 5.9.14 or later.

Summary

(ReDoS) Regular Expression Denial of Service in tf2-item-format

Versions of tf2-item-format since at least 4.2.6 are vulnerable to a Regular Expression Denial of Service (ReDoS) attack when parsing crafted user input.

Tested Versions

5.9.13
5.8.10
5.7.0
5.6.17
4.3.5
4.2.6

v5

Upgrade package to ^5.9.14

v4

No patch exists. Please consult the v4 to v5 migration guide to upgrade to v5.

If upgrading to v5 is not possible, fork the module repository and implement the fix detailed below.

Impact

This vulnerability can be exploited by an attacker to perform DoS attacks on any service that uses any tf2-item-format to parse user input.

A regular expression with worst-case exponential or polynomial matching time is applied to untrusted input, causing excessive CPU use. Typical impact: denial of service when input is crafted to trigger backtracking.

CVE-2024-41655 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. 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 (5.9.14); upgrading removes the vulnerable code path.

Affected versions

tf2-item-format (>= 4.2.6, <= 5.9.13)

Security releases

tf2-item-format → 5.9.14 (npm)

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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade tf2-item-format to 5.9.14 or later to resolve this vulnerability.

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

Frequently Asked Questions

What is CVE-2024-41655? CVE-2024-41655 is a high-severity inefficient regular expression (ReDoS) vulnerability in tf2-item-format (npm), affecting versions >= 4.2.6, <= 5.9.13. It is fixed in 5.9.14. A regular expression with worst-case exponential or polynomial matching time is applied to untrusted input, causing excessive CPU use.
How severe is CVE-2024-41655? CVE-2024-41655 has a CVSS score of 7.5 (High). 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 versions of tf2-item-format are affected by CVE-2024-41655? tf2-item-format (npm) versions >= 4.2.6, <= 5.9.13 is affected.
Is there a fix for CVE-2024-41655? Yes. CVE-2024-41655 is fixed in 5.9.14. Upgrade to this version or later.
Is CVE-2024-41655 exploitable, and should I be worried? Whether CVE-2024-41655 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-2024-41655 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-2024-41655? Upgrade tf2-item-format to 5.9.14 or later.