Medium, CVSS 5.8npmAmendedPublished
Unwanted access to the entire file system vulnerability due to a missing check in staticFiles HTTP handler
CVE-2025-27098 · GHSA-j2wh-wrv3-4x4g
- Affected
- npm @graphql-mesh/http < 0.3.19
- Fixed in
- 0.3.19· Vendor fix available
- Issue
- Missing check vulnerability in the static file handler allows any client to access the files in the server's file system Details When staticFiles is set in the serve settings in the configuration file, the following handler doesn't check if absolutePath is still under the directory provided as staticFiles; Example scenario To reproduce it, set staticFiles to the relative path of a directory in .meshrc.yml; Then start the server with mesh dev, and browse to /..%2fpackage.json then you will see the content of package.json. You can even go deeper to see sensitive data; /..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2fetc/passwd Impact and solution If staticFiles is set under serve in the configuration file. you have two options to fix vulnerability; - Update @graphql-mesh/cli to a version higher than 0.82.21, and if you use @graphql-mesh/http, update it to a version higher than 0.3.18 - Remove staticFiles option from the configuration, and use other solutions to…
Recommended action: Upgrade to 0.3.19 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.