GitHub Advisoryadvisory · npm
GHSA-rr4x-crhf-8886 Cache variables with the operations when transforms exist on the root level even if variables change in the further requests with the same operation
MEDIUM
Official page ↗
- Aliases
- CVE-2025-27097
- Ecosystem
- npm
- Packages
- @graphql-mesh/runtime
- Severity
- Moderate
- CVSS vector
- CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N
- Weaknesses
- CWE-400, CWE-401
- Reviewed
- 2023-10-10
Affected packages
• npm @graphql-mesh/runtime: >= 0.96.5, < 0.96.9 → fixed in 0.96.9
Description
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.
Related
Alias · CVE (1)
- CVE-2025-27097 GraphQL Mesh is a GraphQL Federation framework and gateway for both GraphQL Federation and non-GraphQL Federation subgraphs, non-GraphQL… vulnerability
References
- https://github.com/Urigo/graphql-mesh/security/advisories/GHSA-rr4x-crhf-8886 web
- https://github.com/ardatan/graphql-mesh/security/advisories/GHSA-rr4x-crhf-8886 web
- https://nvd.nist.gov/vuln/detail/CVE-2025-27097 advisory
- https://github.com/Urigo/graphql-mesh/commit/482d813a9f75935024aa77872125d197f5fca3d0 web
- https://github.com/Urigo/graphql-mesh package
- https://github.com/Urigo/graphql-mesh/releases/tag/release-1696859949678 web