<?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://vulnerability.circl.lu</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>Thu, 01 Oct 2026 05:37:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-71464 — Automation-controller: automation-controller-container: automation-controller: schedule and workflowjobtemplatenode scm…</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-71464</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Red Hat Ansible Automation Platform 2.5 for RHEL 8, Red Hat Ansible Automation Platform 2.5 for RHEL 9, Red Hat Ansible Automation Platform 2.6 for RHEL 9, Red Hat Ansible Automation Platform 2.6, Red Hat Ansible Automation Platform 2.7&lt;/p&gt;
&lt;p&gt;LaunchConfigurationBaseSerializer.scm_branch has no
              validate_scm_branch() leading-dash check, unlike
              Project/JobTemplate/JobLaunch serializers. Schedule and
              WFJT Node accept --upload-pack=/bin/id as scm_branch.
              Currently blocked at runtime by jobs.py:1502 ValueError
              check (defense-in-depth), but the API validation gap
              means sole reliance on a task-layer guard. Refactoring
              that guard away would promote this to RCE.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Red Hat Ansible Automation Platform 2.5 for RHEL 8, Red Hat Ansible Automation Platform 2.5 for RHEL 9, Red Hat Ansible Automation Platform 2.6 for RHEL 9, Red Hat Ansible Automation Platform 2.6, Red Hat Ansible Automation Platform 2.7&lt;/p&gt;
&lt;p&gt;LaunchConfigurationBaseSerializer.scm_branch has no
              validate_scm_branch() leading-dash check, unlike
              Project/JobTemplate/JobLaunch serializers. Schedule and
              WFJT Node accept --upload-pack=/bin/id as scm_branch.
              Currently blocked at runtime by jobs.py:1502 ValueError
              check (defense-in-depth), but the API validation gap
              means sole reliance on a task-layer guard. Refactoring
              that guard away would promote this to RCE.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-71464</guid>
    </item>
  </channel>
</rss>
