@graphql-mesh/runtime
Affected
- introduced
0.96.5, fixed0.96.9(semver)
Fixed versions
0.96.9
Fix
- Fixed version
0.96.9npm install @graphql-mesh/[email protected]
Advisory
Also known as: CVE-2025-27097
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.
Medium Basis: The source's own band: MODERATE
0.96.5, fixed 0.96.9 (semver)0.96.9
0.96.9npm install @graphql-mesh/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0