<?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, 16 Nov 2026 20:46:16 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-405538</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-405538</link>
      <description>EUVD-2026-405538</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-405538</guid>
    </item>
    <item>
      <title>fkie_cve-2026-126642</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-126642</link>
      <description>&lt;p&gt;An incorrect authorization flaw was found in AWX, the automation controller component of Red Hat Ansible Automation Platform. The API access classes for JobTemplate and WorkflowJobTemplate do not check the caller&amp;#39;s Credential use_role when assigning the single-valued webhook_credential foreign key: JobTemplateAccess.can_add/can_change and WorkflowJobTemplateAccess.can_change in awx/main/access.py omit the check_related(&amp;#39;webhook_credential&amp;#39;, Credential, ..., role_field=&amp;#39;use_role&amp;#39;) call that UnifiedCredentialsMixin.can_attach performs for the normal many-to-many credentials relationship, and the serializer validates only the credential&amp;#39;s type and namespace. A user who may administer their own job template (or workflow job template) and use its project and inventory can therefore attach a webhook token credential (for example a GitLab token) that they do not have use permission on. The template administrator can retrieve the template&amp;#39;s webhook key; a subsequent webhook event causes AWX to decrypt the attached token and send it in the request header (for GitLab, PRIVATE-TOKEN) to a status URL derived from the event payload, disclosing the victim&amp;#39;s token to a destination the attacker can influence. This may disclose another user&amp;#39;s personal access token and allow whatever actions that token permits.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An incorrect authorization flaw was found in AWX, the automation controller component of Red Hat Ansible Automation Platform. The API access classes for JobTemplate and WorkflowJobTemplate do not check the caller&amp;#39;s Credential use_role when assigning the single-valued webhook_credential foreign key: JobTemplateAccess.can_add/can_change and WorkflowJobTemplateAccess.can_change in awx/main/access.py omit the check_related(&amp;#39;webhook_credential&amp;#39;, Credential, ..., role_field=&amp;#39;use_role&amp;#39;) call that UnifiedCredentialsMixin.can_attach performs for the normal many-to-many credentials relationship, and the serializer validates only the credential&amp;#39;s type and namespace. A user who may administer their own job template (or workflow job template) and use its project and inventory can therefore attach a webhook token credential (for example a GitLab token) that they do not have use permission on. The template administrator can retrieve the template&amp;#39;s webhook key; a subsequent webhook event causes AWX to decrypt the attached token and send it in the request header (for GitLab, PRIVATE-TOKEN) to a status URL derived from the event payload, disclosing the victim&amp;#39;s token to a destination the attacker can influence. This may disclose another user&amp;#39;s personal access token and allow whatever actions that token permits.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-126642</guid>
    </item>
    <item>
      <title>GHSA-c92q-w8v5-r4hp</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-c92q-w8v5-r4hp</link>
      <description>&lt;p&gt;An incorrect authorization flaw was found in AWX, the automation controller component of Red Hat Ansible Automation Platform. The API access classes for JobTemplate and WorkflowJobTemplate do not check the caller&amp;#39;s Credential use_role when assigning the single-valued webhook_credential foreign key: JobTemplateAccess.can_add/can_change and WorkflowJobTemplateAccess.can_change in awx/main/access.py omit the check_related(&amp;#39;webhook_credential&amp;#39;, Credential, ..., role_field=&amp;#39;use_role&amp;#39;) call that UnifiedCredentialsMixin.can_attach performs for the normal many-to-many credentials relationship, and the serializer validates only the credential&amp;#39;s type and namespace. A user who may administer their own job template (or workflow job template) and use its project and inventory can therefore attach a webhook token credential (for example a GitLab token) that they do not have use permission on. The template administrator can retrieve the template&amp;#39;s webhook key; a subsequent webhook event causes AWX to decrypt the attached token and send it in the request header (for GitLab, PRIVATE-TOKEN) to a status URL derived from the event payload, disclosing the victim&amp;#39;s token to a destination the attacker can influence. This may disclose another user&amp;#39;s personal access token and allow whatever actions that token permits.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An incorrect authorization flaw was found in AWX, the automation controller component of Red Hat Ansible Automation Platform. The API access classes for JobTemplate and WorkflowJobTemplate do not check the caller&amp;#39;s Credential use_role when assigning the single-valued webhook_credential foreign key: JobTemplateAccess.can_add/can_change and WorkflowJobTemplateAccess.can_change in awx/main/access.py omit the check_related(&amp;#39;webhook_credential&amp;#39;, Credential, ..., role_field=&amp;#39;use_role&amp;#39;) call that UnifiedCredentialsMixin.can_attach performs for the normal many-to-many credentials relationship, and the serializer validates only the credential&amp;#39;s type and namespace. A user who may administer their own job template (or workflow job template) and use its project and inventory can therefore attach a webhook token credential (for example a GitLab token) that they do not have use permission on. The template administrator can retrieve the template&amp;#39;s webhook key; a subsequent webhook event causes AWX to decrypt the attached token and send it in the request header (for GitLab, PRIVATE-TOKEN) to a status URL derived from the event payload, disclosing the victim&amp;#39;s token to a destination the attacker can influence. This may disclose another user&amp;#39;s personal access token and allow whatever actions that token permits.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-c92q-w8v5-r4hp</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-126642</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-126642</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: ansible, Ubuntu:Pro:16.04:LTS: ansible, Ubuntu:Pro:18.04:LTS: ansible, Ubuntu:Pro:20.04:LTS: ansible, Ubuntu:22.04:LTS: ansible-core, Ubuntu:Pro:22.04:LTS: ansible, Ubuntu:24.04:LTS: ansible, Ubuntu:24.04:LTS: ansible-core, Ubuntu:26.10: ansible, Ubuntu:26.10: ansible-core and 2 more&lt;/p&gt;
&lt;p&gt;An incorrect authorization flaw was found in AWX, the automation controller component of Red Hat Ansible Automation Platform. The API access classes for JobTemplate and WorkflowJobTemplate do not check the caller&amp;#39;s Credential use_role when assigning the single-valued webhook_credential foreign key: JobTemplateAccess.can_add/can_change and WorkflowJobTemplateAccess.can_change in awx/main/access.py omit the check_related(&amp;#39;webhook_credential&amp;#39;, Credential, ..., role_field=&amp;#39;use_role&amp;#39;) call that UnifiedCredentialsMixin.can_attach performs for the normal many-to-many credentials relationship, and the serializer validates only the credential&amp;#39;s type and namespace. A user who may administer their own job template (or workflow job template) and use its project and inventory can therefore attach a webhook token credential (for example a GitLab token) that they do not have use permission on. The template administrator can retrieve the template&amp;#39;s webhook key; a subsequent webhook event causes AWX to decrypt the attached token and send it in the request header (for GitLab, PRIVATE-TOKEN) to a status URL derived from the event payload, disclosing the victim&amp;#39;s token to a destination the attacker can influence. This may disclose another user&amp;#39;s personal access token and allow whatever actions that token permits.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: ansible, Ubuntu:Pro:16.04:LTS: ansible, Ubuntu:Pro:18.04:LTS: ansible, Ubuntu:Pro:20.04:LTS: ansible, Ubuntu:22.04:LTS: ansible-core, Ubuntu:Pro:22.04:LTS: ansible, Ubuntu:24.04:LTS: ansible, Ubuntu:24.04:LTS: ansible-core, Ubuntu:26.10: ansible, Ubuntu:26.10: ansible-core and 2 more&lt;/p&gt;
&lt;p&gt;An incorrect authorization flaw was found in AWX, the automation controller component of Red Hat Ansible Automation Platform. The API access classes for JobTemplate and WorkflowJobTemplate do not check the caller&amp;#39;s Credential use_role when assigning the single-valued webhook_credential foreign key: JobTemplateAccess.can_add/can_change and WorkflowJobTemplateAccess.can_change in awx/main/access.py omit the check_related(&amp;#39;webhook_credential&amp;#39;, Credential, ..., role_field=&amp;#39;use_role&amp;#39;) call that UnifiedCredentialsMixin.can_attach performs for the normal many-to-many credentials relationship, and the serializer validates only the credential&amp;#39;s type and namespace. A user who may administer their own job template (or workflow job template) and use its project and inventory can therefore attach a webhook token credential (for example a GitLab token) that they do not have use permission on. The template administrator can retrieve the template&amp;#39;s webhook key; a subsequent webhook event causes AWX to decrypt the attached token and send it in the request header (for GitLab, PRIVATE-TOKEN) to a status URL derived from the event payload, disclosing the victim&amp;#39;s token to a destination the attacker can influence. This may disclose another user&amp;#39;s personal access token and allow whatever actions that token permits.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-126642</guid>
    </item>
  </channel>
</rss>
