https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 10 Oct 2026 09:19:03 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-227656 EUVD-2026-227656 https://cve.radiocsirt.org/vuln/euvd-2026-227656 https://cve.radiocsirt.org/vuln/fkie_cve-2025-32031 <p>Apollo Gateway provides utilities for combining multiple GraphQL microservices into a single GraphQL endpoint. Prior to 2.10.1, a vulnerability in Apollo Gateway allowed queries with deeply nested and reused named fragments to be prohibitively expensive to query plan, specifically due to internal optimizations being frequently bypassed. The query planner includes an optimization that significantly speeds up planning for applicable GraphQL selections. However, queries with deeply nested and reused named fragments can generate many selections where this optimization does not apply, leading to significantly longer planning times. Because the query planner does not enforce a timeout, a small number of such queries can render gateway inoperable. This could lead to excessive resource consumption and denial of service. This has been remediated in @apollo/gateway version 2.10.1.</p> <p>Apollo Gateway provides utilities for combining multiple GraphQL microservices into a single GraphQL endpoint. Prior to 2.10.1, a vulnerability in Apollo Gateway allowed queries with deeply nested and reused named fragments to be prohibitively expensive to query plan, specifically due to internal optimizations being frequently bypassed. The query planner includes an optimization that significantly speeds up planning for applicable GraphQL selections. However, queries with deeply nested and reused named fragments can generate many selections where this optimization does not apply, leading to significantly longer planning times. Because the query planner does not enforce a timeout, a small number of such queries can render gateway inoperable. This could lead to excessive resource consumption and denial of service. This has been remediated in @apollo/gateway version 2.10.1.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-32031 https://cve.radiocsirt.org/vuln/ghsa-p2q6-pwh5-m6jr <p><strong>Affected:</strong> npm: @apollo/gateway</p> <p># Impact</p> <p>## Summary</p> <p>A vulnerability in Apollo Gateway allowed queries with deeply nested and reused named fragments to be prohibitively expensive to query plan, specifically due to internal optimizations being frequently bypassed. This could lead to excessive resource consumption and denial of service.</p> <p>## Details</p> <p>The query planner includes an optimization that significantly speeds up planning for applicable GraphQL selections. However, queries with deeply nested and reused named fragments can generate many selections where this optimization does not apply, leading to significantly longer planning times. Because the query planner does not enforce a timeout, a small number of such queries can render gateway inoperable.</p> <p>## Fix/Mitigation</p> <p>- A new **Query Optimization Limit** metric has been added: - This metric approximates the number of selections that cannot be skipped by the existing optimization. - The metric is checked against a limit to prevent excessive computation.</p> <p>Given the complexity of query planning optimizations, we will continue refining these solutions based on real-world performance and accuracy tests.</p> <p># Patches</p> <p>This has been remediated in `@apollo/gateway` version 2.10.1.</p> <p># Workarounds</p> <p>No known direct workarounds exist.</p> <p># References</p> <p>[Query Planning Documentation](https://www.apollographql.com/docs/graphos/reference/federation/query-plans)</p> <p>## Acknowledgements</p> <p>We appreciate the efforts of the security community in identifying and improving the p…</p> <p><strong>Affected:</strong> npm: @apollo/gateway</p> <p># Impact</p> <p>## Summary</p> <p>A vulnerability in Apollo Gateway allowed queries with deeply nested and reused named fragments to be prohibitively expensive to query plan, specifically due to internal optimizations being frequently bypassed. This could lead to excessive resource consumption and denial of service.</p> <p>## Details</p> <p>The query planner includes an optimization that significantly speeds up planning for applicable GraphQL selections. However, queries with deeply nested and reused named fragments can generate many selections where this optimization does not apply, leading to significantly longer planning times. Because the query planner does not enforce a timeout, a small number of such queries can render gateway inoperable.</p> <p>## Fix/Mitigation</p> <p>- A new **Query Optimization Limit** metric has been added: - This metric approximates the number of selections that cannot be skipped by the existing optimization. - The metric is checked against a limit to prevent excessive computation.</p> <p>Given the complexity of query planning optimizations, we will continue refining these solutions based on real-world performance and accuracy tests.</p> <p># Patches</p> <p>This has been remediated in `@apollo/gateway` version 2.10.1.</p> <p># Workarounds</p> <p>No known direct workarounds exist.</p> <p># References</p> <p>[Query Planning Documentation](https://www.apollographql.com/docs/graphos/reference/federation/query-plans)</p> <p>## Acknowledgements</p> <p>We appreciate the efforts of the security community in identifying and improving the p…</p> https://cve.radiocsirt.org/vuln/ghsa-p2q6-pwh5-m6jr