What is CVE-2025-27097?

CVE-2025-27097 is a medium-severity uncontrolled resource consumption vulnerability in @graphql-mesh/runtime (npm), affecting versions >= 0.96.5, < 0.96.9. It is fixed in 0.96.9. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

Which versions of @graphql-mesh/runtime are affected by CVE-2025-27097?

@graphql-mesh/runtime (npm) versions >= 0.96.5, < 0.96.9 is affected.

Is there a fix for CVE-2025-27097?

Yes. CVE-2025-27097 is fixed in 0.96.9. Upgrade to this version or later.

Is CVE-2025-27097 exploitable, and should I be worried?

Whether CVE-2025-27097 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-2025-27097 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-2025-27097 in @graphql-mesh/runtime

Q: Which versions of @graphql-mesh/runtime are affected by CVE-2025-27097?

@graphql-mesh/runtime (npm) versions >= 0.96.5, < 0.96.9 is affected.

Q: Is there a fix for CVE-2025-27097?

Yes. CVE-2025-27097 is fixed in 0.96.9. Upgrade to this version or later.

Q: Is CVE-2025-27097 exploitable, and should I be worried?

Whether CVE-2025-27097 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-2025-27097 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-2025-27097?

Upgrade @graphql-mesh/runtime to 0.96.9 or later.

Summary

Cache variables with the operations when transforms exist on the root level even if variables change in the further requests with the same operation

When you have transforms on the root level or single source with transforms, and the client sends the same query with different variables, the initial variables are used in all following requests until the cache evicts DocumentNode.

Let's say if a token is sent via variables, the following requests will act like the same token is sent even if the following requests have different tokens.

This can cause a short memory leak but it won't grow per each request but per different operation until the cache evicts DocumentNode by LRU mechanism.

Impact

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

Affected versions

@graphql-mesh/runtime (>= 0.96.5, < 0.96.9)

Security releases

@graphql-mesh/runtime → 0.96.9 (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 @graphql-mesh/runtime to 0.96.9 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-2025-27097? CVE-2025-27097 is a medium-severity uncontrolled resource consumption vulnerability in @graphql-mesh/runtime (npm), affecting versions >= 0.96.5, < 0.96.9. It is fixed in 0.96.9. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
Which versions of @graphql-mesh/runtime are affected by CVE-2025-27097? @graphql-mesh/runtime (npm) versions >= 0.96.5, < 0.96.9 is affected.
Is there a fix for CVE-2025-27097? Yes. CVE-2025-27097 is fixed in 0.96.9. Upgrade to this version or later.
Is CVE-2025-27097 exploitable, and should I be worried? Whether CVE-2025-27097 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-2025-27097 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-2025-27097? Upgrade @graphql-mesh/runtime to 0.96.9 or later.