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
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| npm | @graphql-mesh/runtime | >= 0.96.5, < 0.96.9 | 0.96.9 |
Details
As written in the advisory (Markdown source, shown as plain text).
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.
References
External links from the advisory. They lead to third-party sites.
- https://github.com/Urigo/graphql-mesh/security/advisories/GHSA-rr4x-crhf-8886
- https://github.com/ardatan/graphql-mesh/security/advisories/GHSA-rr4x-crhf-8886
- https://nvd.nist.gov/vuln/detail/CVE-2025-27097
- https://github.com/Urigo/graphql-mesh/commit/482d813a9f75935024aa77872125d197f5fca3d0
- https://github.com/Urigo/graphql-mesh
- https://github.com/Urigo/graphql-mesh/releases/tag/release-1696859949678