<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T05:20:59.751235+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bdu:2019-00887</id>
    <title>bdu:2019-00887</title>
    <updated>2026-10-04T05:20:59.773037+00:00</updated>
    <content>bdu:2019-00887</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2019-00887"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/brew-ansible-cve-2018-10855</id>
    <title>BREW-ansible-CVE-2018-10855</title>
    <updated>2026-10-04T05:20:59.773076+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: ansible</p>
<p>Ansible 2.5 prior to 2.5.5, and 2.4 prior to 2.4.5, do not honor the no_log task flag for failed tasks. When the no_log flag has been used to protect sensitive data passed to a task from being logged, and that task does not run successfully, Ansible will expose sensitive data in log files and on the terminal of the user running Ansible.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-ansible-cve-2018-10855"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cnvd-2018-12556</id>
    <title>cnvd-2018-12556</title>
    <updated>2026-10-04T05:20:59.773110+00:00</updated>
    <content>cnvd-2018-12556</content>
    <link href="https://cve.radiocsirt.org/vuln/cnvd-2018-12556"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-64852</id>
    <title>EUVD-2026-64852</title>
    <updated>2026-10-04T05:20:59.773125+00:00</updated>
    <content>EUVD-2026-64852</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-64852"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2018-10855</id>
    <title>fkie_cve-2018-10855</title>
    <updated>2026-10-04T05:20:59.773137+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ansible 2.5 prior to 2.5.5, and 2.4 prior to 2.4.5, do not honor the no_log task flag for failed tasks. When the no_log flag has been used to protect sensitive data passed to a task from being logged, and that task does not run successfully, Ansible will expose sensitive data in log files and on the terminal of the user running Ansible.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2018-10855"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-jwcc-j78w-j73w</id>
    <title>GHSA-jwcc-j78w-j73w — Ansible exposes sensitive data in log files and on the terminal</title>
    <updated>2026-10-04T05:20:59.773159+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: ansible</p>
<p>Ansible 2.5 prior to 2.5.5, and 2.4 prior to 2.4.5, do not honor the no_log task flag for failed tasks. When the no_log flag has been used to protect sensitive data passed to a task from being logged, and that task does not run successfully, Ansible will expose sensitive data in log files and on the terminal of the user running Ansible.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-jwcc-j78w-j73w"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2018-10855</id>
    <title>gsd-2018-10855</title>
    <updated>2026-10-04T05:20:59.773182+00:00</updated>
    <content>gsd-2018-10855</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2018-10855"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2019:0238-1</id>
    <title>openSUSE-SU-2019:0238-1 — Security update for ansible</title>
    <updated>2026-10-04T05:20:59.773192+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for ansible</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2019:0238-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2018-42</id>
    <title>PYSEC-2018-42</title>
    <updated>2026-10-04T05:20:59.773212+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: ansible</p>
<p>Ansible 2.5 prior to 2.5.5, and 2.4 prior to 2.4.5, do not honor the no_log task flag for failed tasks. When the no_log flag has been used to protect sensitive data passed to a task from being logged, and that task does not run successfully, Ansible will expose sensitive data in log files and on the terminal of the user running Ansible.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2018-42"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhba-2018:3788</id>
    <title>RHBA-2018:3788 — Red Hat Bug Fix Advisory: Red Hat OpenStack Platform 12 Bug Fix and Enhancement Advisory</title>
    <updated>2026-10-04T05:20:59.773231+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>ansible: Failed tasks do not honour no_log option allowing for secrets to be disclosed in logs ansible: Inventory variables are loaded from current working directory when running ad-hoc command that can lead to code execution ansible: ansible.cfg is being read from current working directory allowing possible code execution</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhba-2018:3788"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2018:4130-1</id>
    <title>SUSE-SU-2018:4130-1 — Security update for ansible</title>
    <updated>2026-10-04T05:20:59.773252+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for ansible</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/suse-su-2018:4130-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2018-10855</id>
    <title>UBUNTU-CVE-2018-10855</title>
    <updated>2026-10-04T05:20:59.773267+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:18.04:LTS: ansible</p>
<p>Ansible 2.5 prior to 2.5.5, and 2.4 prior to 2.4.5, do not honor the no_log task flag for failed tasks. When the no_log flag has been used to protect sensitive data passed to a task from being logged, and that task does not run successfully, Ansible will expose sensitive data in log files and on the terminal of the user running Ansible.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2018-10855"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1809</id>
    <title>WID-SEC-W-2026-1809 — Red Hat Enterprise Linux Virtualization (Ansible) : Schwachstelle ermöglicht Offenlegung von Informationen</title>
    <updated>2026-10-04T05:20:59.773285+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat Enterprise Linux Virtualization (Ansible) ausnutzen, um Informationen offenzulegen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1809"/>
  </entry>
</feed>
