Server file disclosure via static path traversal
Published Feb 20, 2025 · Updated Feb 20, 2025
Path traversal in GraphQL Mesh before @graphql-mesh/cli 0.82.22 and @graphql-mesh/http 0.3.19 allows remote attackers to read server files. The static-file handler joins a URL-supplied relativePath to the staticFiles base and opens the result without proving it remains beneath that base. Exposure requires staticFiles under serve; a traversal request reads files accessible to the server process.
Summary
What happened
Path traversal in GraphQL Mesh before @graphql-mesh/cli 0.82.22 and @graphql-mesh/http 0.3.19 allows remote attackers to read server files. The static-file handler joins a URL-supplied relativePath to the staticFiles base and opens the result without proving it remains beneath that base. Exposure requires staticFiles under serve; a traversal request reads files accessible to the server process.
The record
- CVE
- CVE-2025-27098
- Published
- Feb 20, 2025
- Updated
- Feb 20, 2025
- Vendor
- The Guild
- Product
- GraphQL Mesh
- Classifications
- CWE-22, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 20, 2025CVE publishedPublication date reported by the CVE source.
- Feb 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=@graphql-mesh/cli: >= 0.78.0, < 0.82.22
- Affected versionversion=@graphql-mesh/http: < 0.3.19
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream encoded traversal reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo