@apollo/server vulnerabilities
Core engine for Apollo GraphQL server
- Registry
- npm
- Latest
- 5.5.1
- License
- MIT
5 known advisories
The latest version, 5.5.1, is not affected by any of them. Projects on older versions may be.
npm install @apollo/server@5.5.1Security advisories for @apollo/server
Apollo Server: Browser bug allows for bypass of XS-Search (read-only Cross-Site Request Forgery) prevention
- Affected
- <5.5.0
- Fixed in
- 5.5.0
Apollo Serve vulnerable to Denial of Service with `startStandaloneServer`
- Affected
- >=4.2.0 <4.13.0 · >=5.0.0 <5.4.0
- Fixed in
- 4.13.0, 5.4.0
Prevent logging invalid header values
- Affected
- <4.9.3
- Fixed in
- 4.9.3
@apollo/server vulnerable to unsafe application of Content Security Policy via reused nonces
- Affected
- >=4.7.1 <4.7.4
- Fixed in
- 4.7.4
Batched HTTP requests may set incorrect `cache-control` response header
- Affected
- <4.1.0
- Fixed in
- 4.1.0
Which of your client projects still run an old @apollo/server?
NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other npm packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.