<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T17:19:10.834620+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/cve-2019-10217</id>
    <title>CVE-2019-10217</title>
    <updated>2026-10-02T17:19:11.217079+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Red Hat Ansible</p>
<p>A flaw was found in ansible 2.8.0 before 2.8.4. Fields managing sensitive data should be set as such by no_log feature. Some of these fields in GCP modules are not set properly. service_account_contents() which is common class for all gcp modules is not setting no_log to True. Any sensitive data managed by that function would be leak as an output when running ansible playbooks.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2019-10217"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-p75j-wc34-527c</id>
    <title>GHSA-p75j-wc34-527c — Exposure of Sensitive Information to an Unauthorized Actor in ansible</title>
    <updated>2026-10-02T17:19:11.217319+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: ansible</p>
<p>A flaw was found in ansible 2.8.0 before 2.8.4. Fields managing sensitive data should be set as such by no_log feature. Some of these fields in GCP modules are not set properly. service_account_contents() which is common class for all gcp modules is not setting no_log to True. Any sensitive data managed by that function would be leak as an output when running ansible playbooks.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-p75j-wc34-527c"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/pysec-2019-3</id>
    <title>PYSEC-2019-3</title>
    <updated>2026-10-02T17:19:11.217395+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: ansible</p>
<p>A flaw was found in ansible 2.8.0 before 2.8.4. Fields managing sensitive data should be set as such by no_log feature. Some of these fields in GCP modules are not set properly. service_account_contents() which is common class for all gcp modules is not setting no_log to True. Any sensitive data managed by that function would be leak as an output when running ansible playbooks.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/pysec-2019-3"/>
  </entry>
</feed>
