<?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 11:59:49 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-332332</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-332332</link>
      <description>EUVD-2026-332332</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-332332</guid>
    </item>
    <item>
      <title>fkie_cve-2026-54164</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-54164</link>
      <description>&lt;p&gt;API Platform Core is a system to create hypermedia-driven REST and GraphQL APIs. In versions prior to 4.1.30, 4.2.26 and 4.3.12, the serializer&amp;#39;s AbstractItemNormalizer does not validate the resource type returned when resolving relation IRIs, allowing type confusion where a resource of an unintended type can be silently assigned to a relation property. An attacker who can submit write requests (POST/PUT/PATCH) to an API Platform endpoint with writable relations can supply a relation IRI pointing to a resource of a different type than the relation&amp;#39;s declared class. Because getResourceFromIri() does not pass an $operation to IriConverter::getResourceFromIri(), the is_a type guard at IriConverter.php:86 is skipped. For untyped relation properties (legacy @var-only style), the wrong-typed object is silently assigned, corrupting invariants and potentially feeding downstream logic that assumes the declared type (CWE-843). For typed properties (modern PHP 8.x), the substitution is blocked by Symfony&amp;#39;s PropertyAccessor with an InvalidTypeException. This issue has been fixed in versions 4.1.30, 4.2.26 and 4.3.12.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;API Platform Core is a system to create hypermedia-driven REST and GraphQL APIs. In versions prior to 4.1.30, 4.2.26 and 4.3.12, the serializer&amp;#39;s AbstractItemNormalizer does not validate the resource type returned when resolving relation IRIs, allowing type confusion where a resource of an unintended type can be silently assigned to a relation property. An attacker who can submit write requests (POST/PUT/PATCH) to an API Platform endpoint with writable relations can supply a relation IRI pointing to a resource of a different type than the relation&amp;#39;s declared class. Because getResourceFromIri() does not pass an $operation to IriConverter::getResourceFromIri(), the is_a type guard at IriConverter.php:86 is skipped. For untyped relation properties (legacy @var-only style), the wrong-typed object is silently assigned, corrupting invariants and potentially feeding downstream logic that assumes the declared type (CWE-843). For typed properties (modern PHP 8.x), the substitution is blocked by Symfony&amp;#39;s PropertyAccessor with an InvalidTypeException. This issue has been fixed in versions 4.1.30, 4.2.26 and 4.3.12.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-54164</guid>
    </item>
    <item>
      <title>GHSA-9rjg-x2p2-h68h — API Platform Core: Relation IRIs are not type-checked: a related resource can be denormalised as the wrong resource typ…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9rjg-x2p2-h68h</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: api-platform/core&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The API Platform serializer&amp;#39;s `AbstractItemNormalizer` does not validate the resource type returned when resolving relation IRIs, allowing type confusion where a resource of an unintended type can be silently assigned to a relation property.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker who can submit write requests (POST/PUT/PATCH) to an API Platform endpoint with writable relations can supply a relation IRI pointing to a resource of a different type than the relation&amp;#39;s declared class. Because `getResourceFromIri()` does not pass an `$operation` to `IriConverter::getResourceFromIri()`, the `is_a` type guard at `IriConverter.php:86` is skipped. For untyped relation properties (legacy `@var`-only style), the wrong-typed object is silently assigned, corrupting invariants and potentially feeding downstream logic that assumes the declared type (CWE-843). For typed properties (modern PHP 8.x), the substitution is blocked by Symfony&amp;#39;s PropertyAccessor with an `InvalidTypeException`.&lt;/p&gt;
&lt;p&gt;## Affected versions&lt;/p&gt;
&lt;p&gt;- `api-platform/core` `&amp;lt; 4.1.30`
- `api-platform/core` `&amp;gt;= 4.2.0, &amp;lt; 4.2.26`
- `api-platform/core` `&amp;gt;= 4.3.0, &amp;lt; 4.3.12`&lt;/p&gt;
&lt;p&gt;Older major series (`2.x`, `3.x`) ship the same vulnerable code path and are end-of-life; no fix is planned.&lt;/p&gt;
&lt;p&gt;## Patched versions&lt;/p&gt;
&lt;p&gt;- `4.1.30`
- `4.2.26`
- `4.3.12`&lt;/p&gt;
&lt;p&gt;## Fix&lt;/p&gt;
&lt;p&gt;An `is_a` guard is added inside `AbstractItemNormalizer::getResourceFromIri()` (and the equivalent inline call sites on 4.1) so that a mismatched IRI throws `InvalidArgumentException`, mirroring the op…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: api-platform/core&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The API Platform serializer&amp;#39;s `AbstractItemNormalizer` does not validate the resource type returned when resolving relation IRIs, allowing type confusion where a resource of an unintended type can be silently assigned to a relation property.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker who can submit write requests (POST/PUT/PATCH) to an API Platform endpoint with writable relations can supply a relation IRI pointing to a resource of a different type than the relation&amp;#39;s declared class. Because `getResourceFromIri()` does not pass an `$operation` to `IriConverter::getResourceFromIri()`, the `is_a` type guard at `IriConverter.php:86` is skipped. For untyped relation properties (legacy `@var`-only style), the wrong-typed object is silently assigned, corrupting invariants and potentially feeding downstream logic that assumes the declared type (CWE-843). For typed properties (modern PHP 8.x), the substitution is blocked by Symfony&amp;#39;s PropertyAccessor with an `InvalidTypeException`.&lt;/p&gt;
&lt;p&gt;## Affected versions&lt;/p&gt;
&lt;p&gt;- `api-platform/core` `&amp;lt; 4.1.30`
- `api-platform/core` `&amp;gt;= 4.2.0, &amp;lt; 4.2.26`
- `api-platform/core` `&amp;gt;= 4.3.0, &amp;lt; 4.3.12`&lt;/p&gt;
&lt;p&gt;Older major series (`2.x`, `3.x`) ship the same vulnerable code path and are end-of-life; no fix is planned.&lt;/p&gt;
&lt;p&gt;## Patched versions&lt;/p&gt;
&lt;p&gt;- `4.1.30`
- `4.2.26`
- `4.3.12`&lt;/p&gt;
&lt;p&gt;## Fix&lt;/p&gt;
&lt;p&gt;An `is_a` guard is added inside `AbstractItemNormalizer::getResourceFromIri()` (and the equivalent inline call sites on 4.1) so that a mismatched IRI throws `InvalidArgumentException`, mirroring the op…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9rjg-x2p2-h68h</guid>
    </item>
  </channel>
</rss>
