<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-10T09:26:53.308088+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-227577</id>
    <title>EUVD-2026-227577</title>
    <updated>2026-10-10T09:26:53.310018+00:00</updated>
    <content>EUVD-2026-227577</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-227577"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-32034</id>
    <title>fkie_cve-2025-32034</title>
    <updated>2026-10-10T09:26:53.310050+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>The Apollo Router Core is a configurable, high-performance graph router written in Rust to run a federated supergraph that uses Apollo Federation 2. Prior to 1.61.2 and 2.1.1, a vulnerability in Apollo Router allowed queries with deeply nested and reused named fragments to be prohibitively expensive to query plan, specifically during named fragment expansion. Named fragments were being expanded once per fragment spread during query planning, leading to exponential resource usage when deeply nested and reused fragments were involved. This could lead to excessive resource consumption and denial of service. This has been remediated in apollo-router versions 1.61.2 and 2.1.1.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-32034"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-75m2-jhh5-j5g2</id>
    <title>GHSA-75m2-jhh5-j5g2 — Apollo Router Query Planner Vulnerable to Excessive Resource Consumption via Named Fragment Expansion</title>
    <updated>2026-10-10T09:26:53.310084+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: apollo-router</p>
<p># Impact</p>
<p>## Summary</p>
<p>A vulnerability in Apollo Router allowed queries with deeply nested and reused named fragments to be prohibitively expensive to query plan, specifically during named fragment expansion. This could lead to excessive resource consumption and denial of service.</p>
<p>## Details</p>
<p>Named fragments were being expanded once per fragment spread during query planning, leading to exponential resource usage when deeply nested and reused fragments were involved.</p>
<p>## Fix/Mitigation</p>
<p>A new **Query Fragment Expansion Limit** metric has been introduced:
  - This metric computes the number of selections a query would have if its fragment spreads were fully expanded.
  - The metric is checked against a limit to prevent excessive computation.</p>
<p># Patches</p>
<p>This has been remediated in `apollo-router` versions 1.61.2 and 2.1.1.</p>
<p># Workarounds</p>
<p>The only known workaround is "Safelisting" or "Safelisting with IDs only" per [Safelisting with Persisted Queries - Apollo GraphQL Docs](https://www.apollographql.com/docs/graphos/routing/security/persisted-queries#router-security-levels).</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 performance and security of query planning mechanisms.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-75m2-jhh5-j5g2"/>
  </entry>
</feed>
