What is CVE-2018-25074?

CVE-2018-25074 is a high-severity inefficient regular expression (ReDoS) vulnerability in skeemas (npm), affecting versions < 1.2.5. It is fixed in 1.2.5. A regular expression with worst-case exponential or polynomial matching time is applied to untrusted input, causing excessive CPU use.

How severe is CVE-2018-25074?

CVE-2018-25074 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 skeemas are affected by CVE-2018-25074?

skeemas (npm) versions < 1.2.5 is affected.

Is there a fix for CVE-2018-25074?

Yes. CVE-2018-25074 is fixed in 1.2.5. Upgrade to this version or later.

Is CVE-2018-25074 exploitable, and should I be worried?

Whether CVE-2018-25074 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-2018-25074 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-2018-25074 in skeemas

Q: How severe is CVE-2018-25074?

CVE-2018-25074 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 skeemas are affected by CVE-2018-25074?

skeemas (npm) versions < 1.2.5 is affected.

Q: Is there a fix for CVE-2018-25074?

Yes. CVE-2018-25074 is fixed in 1.2.5. Upgrade to this version or later.

Q: Is CVE-2018-25074 exploitable, and should I be worried?

Whether CVE-2018-25074 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-2018-25074 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-2018-25074?

Upgrade skeemas to 1.2.5 or later.

Summary

skeemas Inefficient Regular Expression Complexity vulnerability

A vulnerability was found in Prestaul skeemas and classified as problematic. This issue affects some unknown processing of the file validators/base.js. The manipulation of the argument uri leads to inefficient regular expression complexity. The name of the patch is 65e94eda62dc8dc148ab3e59aa2ccc086ac448fd. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-218003.

Impact

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-2018-25074 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 (1.2.5); upgrading removes the vulnerable code path.

Affected versions

skeemas (< 1.2.5)

Security releases

skeemas → 1.2.5 (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 skeemas to 1.2.5 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-2018-25074? CVE-2018-25074 is a high-severity inefficient regular expression (ReDoS) vulnerability in skeemas (npm), affecting versions < 1.2.5. It is fixed in 1.2.5. A regular expression with worst-case exponential or polynomial matching time is applied to untrusted input, causing excessive CPU use.
How severe is CVE-2018-25074? CVE-2018-25074 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 skeemas are affected by CVE-2018-25074? skeemas (npm) versions < 1.2.5 is affected.
Is there a fix for CVE-2018-25074? Yes. CVE-2018-25074 is fixed in 1.2.5. Upgrade to this version or later.
Is CVE-2018-25074 exploitable, and should I be worried? Whether CVE-2018-25074 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-2018-25074 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-2018-25074? Upgrade skeemas to 1.2.5 or later.