<?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-11-16T18:45:34.119872+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/brew-moto-cve-2026-75507</id>
    <title>BREW-moto-CVE-2026-75507 — GraphQL-core: Denial of service via quadratic complexity in the OverlappingFieldsCanBeMerged validation rule</title>
    <updated>2026-11-16T18:45:34.384916+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: moto</p>
<p>### Summary</p>
<p>The `OverlappingFieldsCanBeMerged` validation rule can be driven into quadratic — and
in the worst case `O(n²·m²)` — running time by a small, highly compressible query. A
single 364 KB document can occupy one CPU core for over five minutes during
*validation*, before any resolver runs. Because the rule is part of `specified_rules`
and therefore enabled by default, every GraphQL-core based server is affected at
default settings.</p>
<p>### Details</p>
<p>`OverlappingFieldsCanBeMerged` compares every pair of fields that share a response
name and recurses into their sub-selections. The memoization added for
CVE-2023-26144 (`GHSA-9pv7-vfvm-6vr7`) is keyed by **named fragment** identity, so it
does not cover this path: inline fragments are flattened into the parent selection
set before the cache is consulted, and therefore every pair is re-compared from
scratch at every nesting level.</p>
<p>Repeating an inline fragment that selects the same response name at two nesting
levels multiplies the two effects. There was no comparison budget and no validation
timeout, so the rule ran to completion regardless of cost.</p>
<p>The cost is incurred in the **validation phase**, which is what makes this hard to
defend against from outside the library: query-depth limiters, complexity analyzers
and cost estimators all operate on the parsed document *after* validation, and the
malicious document is trivially shallow (depth 3, complexity 1). The payload is also
one short string repeated many times, so it c…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-moto-cve-2026-75507"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-391799</id>
    <title>EUVD-2026-391799</title>
    <updated>2026-11-16T18:45:34.385004+00:00</updated>
    <content>EUVD-2026-391799</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-391799"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-75507</id>
    <title>fkie_cve-2026-75507</title>
    <updated>2026-11-16T18:45:34.385021+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>GraphQL-core is a Python port of the GraphQL.js reference implementation. From 3.0.0 until 3.2.12 and 3.3.0rc1, the OverlappingFieldsCanBeMerged rule in specified_rules repeatedly compares fields that share response names and recursively re-compares flattened inline fragments during the validation phase. The prior named-fragment memoization does not cover this path, so nested repeated inline fragments can drive quadratic and worst-case O(n²·m²) CPU work before any resolver or AST-based depth or complexity control runs. An unauthenticated remote attacker can submit a shallow, highly compressible GraphQL query that pins a worker process and can saturate a multi-worker service. This issue is fixed in versions 3.2.12 and 3.3.0rc1.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-75507"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-vj8h-fx38-h3vc</id>
    <title>GHSA-vj8h-fx38-h3vc — GraphQL-core: Denial of service via quadratic complexity in the OverlappingFieldsCanBeMerged validation rule</title>
    <updated>2026-11-16T18:45:34.385048+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: graphql-core</p>
<p>### Summary</p>
<p>The `OverlappingFieldsCanBeMerged` validation rule can be driven into quadratic — and
in the worst case `O(n²·m²)` — running time by a small, highly compressible query. A
single 364 KB document can occupy one CPU core for over five minutes during
*validation*, before any resolver runs. Because the rule is part of `specified_rules`
and therefore enabled by default, every GraphQL-core based server is affected at
default settings.</p>
<p>### Details</p>
<p>`OverlappingFieldsCanBeMerged` compares every pair of fields that share a response
name and recurses into their sub-selections. The memoization added for
CVE-2023-26144 (`GHSA-9pv7-vfvm-6vr7`) is keyed by **named fragment** identity, so it
does not cover this path: inline fragments are flattened into the parent selection
set before the cache is consulted, and therefore every pair is re-compared from
scratch at every nesting level.</p>
<p>Repeating an inline fragment that selects the same response name at two nesting
levels multiplies the two effects. There was no comparison budget and no validation
timeout, so the rule ran to completion regardless of cost.</p>
<p>The cost is incurred in the **validation phase**, which is what makes this hard to
defend against from outside the library: query-depth limiters, complexity analyzers
and cost estimators all operate on the parsed document *after* validation, and the
malicious document is trivially shallow (depth 3, complexity 1). The payload is also
one short string repeated many times, so it c…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-vj8h-fx38-h3vc"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2026:95872</id>
    <title>RHSA-2026:95872 — Red Hat Security Advisory: RHOAI 3.5.3 - Red Hat OpenShift AI</title>
    <updated>2026-11-16T18:45:34.385099+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>markdown: python-markdown: Denial of Service via inefficient inline link parsing undici: undici: Information disclosure and Denial of Service via malformed Cache-Control directives @fastify/static: @fastify/static: Information disclosure via route guard bypass fast-uri: fast-uri: Host confusion vulnerability via backslash in URI authority undici: undici: Denial of Service via unrequested WebSocket subprotocol extract-zip: extract-zip: Arbitrary file write via symlink in archive encoding/asn1: golang: Go encoding/asn1: Denial of Service via excessive recursion in Unmarshal find-my-way: find-my-way: Denial of Service vulnerability in HTTP/2 server systeminformation: systeminformation: Arbitrary Command Execution via OS Command Injection mlflow: mlflow: Arbitrary file write via FileStore path traversal mcp: mcp: Denial of Service via session memory exhaustion in streamable HTTP servers nltk: NLTK: Information Disclosure via Symlink Sandbox Bypass github.com/klauspost/compress: klauspost/compress: Denial of Service via integer overflow in dictionary processing com.fasterxml.jackson.core/jackson-core: tools.jackson.core/jackson-core: jackson-core: Denial of Service via excessively long JSON property names accelerate: Hugging Face Accelerate: Path Traversal and Denial of Service via weight_map brace-expansion: DoS via unbounded intermediate arrays, bypassing the CVE-2026-14257 mitigation aiohttp: AIOHTTP: HTTP Request Smuggling via WebSocket Upgrade aiohttp: AIOHTTP: Denial of Ser…</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2026:95872"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-75507</id>
    <title>UBUNTU-CVE-2026-75507</title>
    <updated>2026-11-16T18:45:34.385484+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:22.04:LTS: graphql-core, Ubuntu:24.04:LTS: graphql-core, Ubuntu:26.10: graphql-core, Ubuntu:26.04:LTS: graphql-core</p>
<p>GraphQL-core is a Python port of the GraphQL.js reference implementation. From 3.0.0 until 3.2.12 and 3.3.0rc1, the OverlappingFieldsCanBeMerged rule in specified_rules repeatedly compares fields that share response names and recursively re-compares flattened inline fragments during the validation phase. The prior named-fragment memoization does not cover this path, so nested repeated inline fragments can drive quadratic and worst-case O(n²·m²) CPU work before any resolver or AST-based depth or complexity control runs. An unauthenticated remote attacker can submit a shallow, highly compressible GraphQL query that pins a worker process and can saturate a multi-worker service. This issue is fixed in versions 3.2.12 and 3.3.0rc1.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-75507"/>
  </entry>
</feed>
