<?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>Mon, 19 Oct 2026 05:55:20 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-281173</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-281173</link>
      <description>EUVD-2026-281173</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-281173</guid>
    </item>
    <item>
      <title>fkie_cve-2026-39397</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-39397</link>
      <description>&lt;p&gt;@delmaredigital/payload-puck is a PayloadCMS plugin for integrating Puck visual page builder. Prior to 0.6.23, all /api/puck/* CRUD endpoint handlers registered by createPuckPlugin() called Payload&amp;#39;s local API with the default overrideAccess: true, bypassing all collection-level access control. The access option passed to createPuckPlugin() and any access rules defined on Puck-registered collections were silently ignored on these endpoints. This vulnerability is fixed in 0.6.23.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;@delmaredigital/payload-puck is a PayloadCMS plugin for integrating Puck visual page builder. Prior to 0.6.23, all /api/puck/* CRUD endpoint handlers registered by createPuckPlugin() called Payload&amp;#39;s local API with the default overrideAccess: true, bypassing all collection-level access control. The access option passed to createPuckPlugin() and any access rules defined on Puck-registered collections were silently ignored on these endpoints. This vulnerability is fixed in 0.6.23.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-39397</guid>
    </item>
    <item>
      <title>GHSA-65w6-pf7x-5g85 — @delmaredigital/payload-puc is missing authorization on /api/puck/* CRUD endpoints allows unauthenticated access to Puc…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-65w6-pf7x-5g85</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @delmaredigital/payload-puck&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;All `/api/puck/*` CRUD endpoint handlers registered by `createPuckPlugin()` called Payload&amp;#39;s local API with the default `overrideAccess: true`, bypassing all collection-level access control. The `access` option passed to `createPuckPlugin()` and any `access` rules defined on Puck-registered collections were silently ignored on these endpoints.&lt;/p&gt;
&lt;p&gt;An unauthenticated remote attacker could:&lt;/p&gt;
&lt;p&gt;- List all documents (including drafts) in any Puck-registered collection
- Read any document by ID (including drafts)
- Create new documents with arbitrary field values
- Update any document (including bypassing field-level access rules)
- Delete any document
- Read version history and restore arbitrary versions&lt;/p&gt;
&lt;p&gt;**In typical installations**, the affected scope is the collection backing the website&amp;#39;s pages (default slug: `pages`). For most users this means an attacker could read, modify, create, or delete every page on the website — including unpublished drafts and version history.&lt;/p&gt;
&lt;p&gt;**Scope is limited to collections explicitly registered with `createPuckPlugin()`** — the endpoints validate the collection slug against an allowlist, so attackers cannot pivot to other Payload collections such as `users`, `media`, or business data not exposed to the plugin. The auto-created `puck-templates`, `puck-ai-prompts`, and `puck-ai-context` collections are also outside the allowlist; they have their own dedicated endpoints with separate authentication.&lt;/p&gt;
&lt;p&gt;Other endpoints in the plugin (AI, styl…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @delmaredigital/payload-puck&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;All `/api/puck/*` CRUD endpoint handlers registered by `createPuckPlugin()` called Payload&amp;#39;s local API with the default `overrideAccess: true`, bypassing all collection-level access control. The `access` option passed to `createPuckPlugin()` and any `access` rules defined on Puck-registered collections were silently ignored on these endpoints.&lt;/p&gt;
&lt;p&gt;An unauthenticated remote attacker could:&lt;/p&gt;
&lt;p&gt;- List all documents (including drafts) in any Puck-registered collection
- Read any document by ID (including drafts)
- Create new documents with arbitrary field values
- Update any document (including bypassing field-level access rules)
- Delete any document
- Read version history and restore arbitrary versions&lt;/p&gt;
&lt;p&gt;**In typical installations**, the affected scope is the collection backing the website&amp;#39;s pages (default slug: `pages`). For most users this means an attacker could read, modify, create, or delete every page on the website — including unpublished drafts and version history.&lt;/p&gt;
&lt;p&gt;**Scope is limited to collections explicitly registered with `createPuckPlugin()`** — the endpoints validate the collection slug against an allowlist, so attackers cannot pivot to other Payload collections such as `users`, `media`, or business data not exposed to the plugin. The auto-created `puck-templates`, `puck-ai-prompts`, and `puck-ai-context` collections are also outside the allowlist; they have their own dedicated endpoints with separate authentication.&lt;/p&gt;
&lt;p&gt;Other endpoints in the plugin (AI, styl…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-65w6-pf7x-5g85</guid>
    </item>
  </channel>
</rss>
