CVE-2025-27097
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGraphQL Mesh is a GraphQL Federation framework and gateway for both GraphQL Federation and non-GraphQL Federation subgraphs, non-GraphQL services, such as REST and gRPC, and also databases such as MongoDB, MySQL, and PostgreSQL. When a user 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. 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGraphQL Mesh incorrectly caches DocumentNode objects by query text only, ignoring variable differences. When the same query is executed with different variables (including authentication tokens), the initial variables persist across subsequent requests until cache eviction, causing potential authentication/authorization bypass.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 0.96.5= 0.96.6= 0.96.7= 0.96.8CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify GraphQL Mesh versionRun `npm list @graphql-mesh/core` or check package.json dependencies to identify the installed version of @graphql-mesh/coreAffected if The installed version is 0.96.5, 0.96.6, 0.96.7, or 0.96.8
-
Confirm caching is enabledInspect your GraphQL Mesh configuration file (typically mesh.config.js or mesh.yaml) for cache settings. Look for cache configurations under the sources or additionalEnvelopPlugins sectionsAffected if Caching is enabled and configured in the mesh configuration
-
Identify queries using variables for authenticationReview your GraphQL query definitions and client code to determine if authentication tokens, authorization headers, or other sensitive data are passed as query variables (e.g., $token, $authToken, $sessionId)Affected if Queries pass authentication or authorization data through GraphQL query variables rather than HTTP headers
-
Check for cross-request variable leakageExecute the same GraphQL query twice using different variable values (e.g., different authentication tokens). Inspect the response to verify if the second request returns data associated with the first request's variablesAffected if The second request returns results corresponding to the first request's variables instead of the second request's variables
You are affected if you are using GraphQL Mesh version 0.96.5-0.96.8, have caching enabled, and pass sensitive data like authentication tokens via GraphQL query variables.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedImplement variable-aware caching by including variable values in the cache key, or disable caching for queries containing sensitive variables (e.g., tokens in variables). Until patch is available, avoid passing authentication tokens via GraphQL query variables.
0.96.9 or later
- 1. Update your package.json to use Graphql Mesh version 0.96.9 or later
- 2. Run npm update @graphql-mesh/core or yarn upgrade @graphql-mesh/core to apply the update
- 3. Verify the installation by checking npm list @graphql-mesh/core or yarn list @graphql-mesh/core
- 4. Test your application to confirm the variable caching issue is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27097 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-27097 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data