<?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://db.gcve.eu</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>Fri, 23 Oct 2026 09:34:53 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-114077</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-114077</link>
      <description>&lt;p&gt;Trigger.dev before 4.5.6 contains an authorization bypass vulnerability in createDeploymentBackgroundWorkerV4 that resolves a WorkerDeployment by friendlyId alone, without environment, project, or organization scoping. Attackers holding only their own environment API key can POST to the deployment background-workers endpoint with a victim&amp;#39;s deployment ID to re-point that in-progress deployment at a worker in the attacker&amp;#39;s environment.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Trigger.dev before 4.5.6 contains an authorization bypass vulnerability in createDeploymentBackgroundWorkerV4 that resolves a WorkerDeployment by friendlyId alone, without environment, project, or organization scoping. Attackers holding only their own environment API key can POST to the deployment background-workers endpoint with a victim&amp;#39;s deployment ID to re-point that in-progress deployment at a worker in the attacker&amp;#39;s environment.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-114077</guid>
    </item>
    <item>
      <title>GHSA-r27f-m68x-3cjm</title>
      <link>https://db.gcve.eu/vuln/ghsa-r27f-m68x-3cjm</link>
      <description>&lt;p&gt;Trigger.dev before 4.5.6 contains an authorization bypass vulnerability in createDeploymentBackgroundWorkerV4 that resolves a WorkerDeployment by friendlyId alone, without environment, project, or organization scoping. Attackers holding only their own environment API key can POST to the deployment background-workers endpoint with a victim&amp;#39;s deployment ID to re-point that in-progress deployment at a worker in the attacker&amp;#39;s environment.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Trigger.dev before 4.5.6 contains an authorization bypass vulnerability in createDeploymentBackgroundWorkerV4 that resolves a WorkerDeployment by friendlyId alone, without environment, project, or organization scoping. Attackers holding only their own environment API key can POST to the deployment background-workers endpoint with a victim&amp;#39;s deployment ID to re-point that in-progress deployment at a worker in the attacker&amp;#39;s environment.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-r27f-m68x-3cjm</guid>
    </item>
  </channel>
</rss>
