<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 07 Oct 2026 05:53:12 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-209888</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-209888</link>
      <description>EUVD-2026-209888</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-209888</guid>
    </item>
    <item>
      <title>fkie_cve-2025-22151</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-22151</link>
      <description>&lt;p&gt;Strawberry GraphQL is a library for creating GraphQL APIs. Starting in 0.182.0 and prior to version 0.257.0, a type confusion vulnerability exists in Strawberry GraphQL&amp;#39;s relay integration that affects multiple ORM integrations (Django, SQLAlchemy, Pydantic). The vulnerability occurs when multiple GraphQL types are mapped to the same underlying model while using the relay node interface. When querying for a specific type using the global node field (e.g., FruitType:some-id), the resolver may incorrectly return an instance of a different type mapped to the same model (e.g., SpecialFruitType). This can lead to information disclosure if the alternate type exposes sensitive fields and potential privilege escalation if the alternate type contains data intended for restricted access. This vulnerability is fixed in 0.257.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Strawberry GraphQL is a library for creating GraphQL APIs. Starting in 0.182.0 and prior to version 0.257.0, a type confusion vulnerability exists in Strawberry GraphQL&amp;#39;s relay integration that affects multiple ORM integrations (Django, SQLAlchemy, Pydantic). The vulnerability occurs when multiple GraphQL types are mapped to the same underlying model while using the relay node interface. When querying for a specific type using the global node field (e.g., FruitType:some-id), the resolver may incorrectly return an instance of a different type mapped to the same model (e.g., SpecialFruitType). This can lead to information disclosure if the alternate type exposes sensitive fields and potential privilege escalation if the alternate type contains data intended for restricted access. This vulnerability is fixed in 0.257.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-22151</guid>
    </item>
    <item>
      <title>GHSA-5xh2-23cc-5jc6 — Strawberry GraphQL has type resolution vulnerability in node interface that allows potential data leakage through incor…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5xh2-23cc-5jc6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: strawberry-graphql&lt;/p&gt;
&lt;p&gt;**Vulnerability Summary**
A type confusion vulnerability exists in Strawberry GraphQL&amp;#39;s relay integration that affects multiple ORM integrations (Django, SQLAlchemy, Pydantic). The vulnerability occurs when multiple GraphQL types are mapped to the same underlying model while using the relay `node` interface.&lt;/p&gt;
&lt;p&gt;**Affected Components**
- Strawberry GraphQL relay integration
- Specifically impacts implementations using:
  - Django integration
  - SQLAlchemy integration
  - Pydantic integration&lt;/p&gt;
&lt;p&gt;**Technical Details**&lt;/p&gt;
&lt;p&gt;The vulnerability manifests when:
1. Multiple GraphQL types inherit from `relay.Node`
2. These types are mapped to the same database model
3. The global `node` field is used for type resolution&lt;/p&gt;
&lt;p&gt;Example of vulnerable code:&lt;/p&gt;
&lt;p&gt;```python
from fruits.models import Fruit
import strawberry_django
import strawberry&lt;/p&gt;
&lt;p&gt;@strawberry_django.type(Fruit)
class FruitType(relay.Node):
    name: strawberry.auto&lt;/p&gt;
&lt;p&gt;@strawberry_django.type(Fruit)
class SpecialFruitType(relay.Node):
    secret_name: strawberry.auto&lt;/p&gt;
&lt;p&gt;@strawberry.type
class Query:
    node: relay.Node = strawberry_django.node()
```&lt;/p&gt;
&lt;p&gt;**Security Impact**&lt;/p&gt;
&lt;p&gt;When querying for a specific type using the global `node` field (e.g., `FruitType:some-id`), the resolver may incorrectly return an instance of a different type mapped to the same model (e.g., `SpecialFruitType`). This can lead to:&lt;/p&gt;
&lt;p&gt;1. Information disclosure if the alternate type exposes sensitive fields
2. Potential privilege escalation if the alternate type contains data in…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: strawberry-graphql&lt;/p&gt;
&lt;p&gt;**Vulnerability Summary**
A type confusion vulnerability exists in Strawberry GraphQL&amp;#39;s relay integration that affects multiple ORM integrations (Django, SQLAlchemy, Pydantic). The vulnerability occurs when multiple GraphQL types are mapped to the same underlying model while using the relay `node` interface.&lt;/p&gt;
&lt;p&gt;**Affected Components**
- Strawberry GraphQL relay integration
- Specifically impacts implementations using:
  - Django integration
  - SQLAlchemy integration
  - Pydantic integration&lt;/p&gt;
&lt;p&gt;**Technical Details**&lt;/p&gt;
&lt;p&gt;The vulnerability manifests when:
1. Multiple GraphQL types inherit from `relay.Node`
2. These types are mapped to the same database model
3. The global `node` field is used for type resolution&lt;/p&gt;
&lt;p&gt;Example of vulnerable code:&lt;/p&gt;
&lt;p&gt;```python
from fruits.models import Fruit
import strawberry_django
import strawberry&lt;/p&gt;
&lt;p&gt;@strawberry_django.type(Fruit)
class FruitType(relay.Node):
    name: strawberry.auto&lt;/p&gt;
&lt;p&gt;@strawberry_django.type(Fruit)
class SpecialFruitType(relay.Node):
    secret_name: strawberry.auto&lt;/p&gt;
&lt;p&gt;@strawberry.type
class Query:
    node: relay.Node = strawberry_django.node()
```&lt;/p&gt;
&lt;p&gt;**Security Impact**&lt;/p&gt;
&lt;p&gt;When querying for a specific type using the global `node` field (e.g., `FruitType:some-id`), the resolver may incorrectly return an instance of a different type mapped to the same model (e.g., `SpecialFruitType`). This can lead to:&lt;/p&gt;
&lt;p&gt;1. Information disclosure if the alternate type exposes sensitive fields
2. Potential privilege escalation if the alternate type contains data in…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5xh2-23cc-5jc6</guid>
    </item>
    <item>
      <title>PYSEC-2026-1946 — Strawberry GraphQL has type resolution vulnerability in node interface that allows potential data leakage through incor…</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-1946</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: strawberry-graphql&lt;/p&gt;
&lt;p&gt;**Vulnerability Summary**
A type confusion vulnerability exists in Strawberry GraphQL&amp;#39;s relay integration that affects multiple ORM integrations (Django, SQLAlchemy, Pydantic). The vulnerability occurs when multiple GraphQL types are mapped to the same underlying model while using the relay `node` interface.&lt;/p&gt;
&lt;p&gt;**Affected Components**
- Strawberry GraphQL relay integration
- Specifically impacts implementations using:
  - Django integration
  - SQLAlchemy integration
  - Pydantic integration&lt;/p&gt;
&lt;p&gt;**Technical Details**&lt;/p&gt;
&lt;p&gt;The vulnerability manifests when:
1. Multiple GraphQL types inherit from `relay.Node`
2. These types are mapped to the same database model
3. The global `node` field is used for type resolution&lt;/p&gt;
&lt;p&gt;Example of vulnerable code:&lt;/p&gt;
&lt;p&gt;```python
from fruits.models import Fruit
import strawberry_django
import strawberry&lt;/p&gt;
&lt;p&gt;@strawberry_django.type(Fruit)
class FruitType(relay.Node):
    name: strawberry.auto&lt;/p&gt;
&lt;p&gt;@strawberry_django.type(Fruit)
class SpecialFruitType(relay.Node):
    secret_name: strawberry.auto&lt;/p&gt;
&lt;p&gt;@strawberry.type
class Query:
    node: relay.Node = strawberry_django.node()
```&lt;/p&gt;
&lt;p&gt;**Security Impact**&lt;/p&gt;
&lt;p&gt;When querying for a specific type using the global `node` field (e.g., `FruitType:some-id`), the resolver may incorrectly return an instance of a different type mapped to the same model (e.g., `SpecialFruitType`). This can lead to:&lt;/p&gt;
&lt;p&gt;1. Information disclosure if the alternate type exposes sensitive fields
2. Potential privilege escalation if the alternate type contains data in…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: strawberry-graphql&lt;/p&gt;
&lt;p&gt;**Vulnerability Summary**
A type confusion vulnerability exists in Strawberry GraphQL&amp;#39;s relay integration that affects multiple ORM integrations (Django, SQLAlchemy, Pydantic). The vulnerability occurs when multiple GraphQL types are mapped to the same underlying model while using the relay `node` interface.&lt;/p&gt;
&lt;p&gt;**Affected Components**
- Strawberry GraphQL relay integration
- Specifically impacts implementations using:
  - Django integration
  - SQLAlchemy integration
  - Pydantic integration&lt;/p&gt;
&lt;p&gt;**Technical Details**&lt;/p&gt;
&lt;p&gt;The vulnerability manifests when:
1. Multiple GraphQL types inherit from `relay.Node`
2. These types are mapped to the same database model
3. The global `node` field is used for type resolution&lt;/p&gt;
&lt;p&gt;Example of vulnerable code:&lt;/p&gt;
&lt;p&gt;```python
from fruits.models import Fruit
import strawberry_django
import strawberry&lt;/p&gt;
&lt;p&gt;@strawberry_django.type(Fruit)
class FruitType(relay.Node):
    name: strawberry.auto&lt;/p&gt;
&lt;p&gt;@strawberry_django.type(Fruit)
class SpecialFruitType(relay.Node):
    secret_name: strawberry.auto&lt;/p&gt;
&lt;p&gt;@strawberry.type
class Query:
    node: relay.Node = strawberry_django.node()
```&lt;/p&gt;
&lt;p&gt;**Security Impact**&lt;/p&gt;
&lt;p&gt;When querying for a specific type using the global `node` field (e.g., `FruitType:some-id`), the resolver may incorrectly return an instance of a different type mapped to the same model (e.g., `SpecialFruitType`). This can lead to:&lt;/p&gt;
&lt;p&gt;1. Information disclosure if the alternate type exposes sensitive fields
2. Potential privilege escalation if the alternate type contains data in…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-1946</guid>
    </item>
  </channel>
</rss>
