<?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-09T19:14:06.528156+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/fkie_cve-2019-17110</id>
    <title>fkie_cve-2019-17110</title>
    <updated>2026-10-09T19:14:07.370311+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2019-10223. Reason: This candidate is a duplicate of CVE-2019-10223. Notes: All CVE users should reference CVE-2019-10223 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2019-17110"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-2v6x-frw8-7r7f</id>
    <title>Withdrawn: GHSA-2v6x-frw8-7r7f — Duplicate Advisory: k8s.io/kube-state-metrics Exposure of Sensitive Information</title>
    <updated>2026-10-09T19:14:07.370409+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Withdrawn by the publisher.</strong></p>
<p><strong>Affected:</strong> Go: github.com/kubernetes/kube-state-metrics, Go: k8s.io/kube-state-metrics</p>
<p># Duplicate Advisory</p>
<p>This advisory has been withdrawn because it is a duplicate of GHSA-c92w-72c5-9x59. This link is maintained to preserve external references.</p>
<p># Original Description</p>
<p>A security issue was discovered in kube-state-metrics 1.7.x before 1.7.2. An experimental feature was added to v1.7.0 and v1.7.1 that enabled annotations to be exposed as metrics. By default, kube-state-metrics metrics only expose metadata about Secrets. However, a combination of the default kubectl behavior and this new feature can cause the entire secret content to end up in metric labels, thus inadvertently exposing the secret content in metrics.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-2v6x-frw8-7r7f"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/gsd-2019-17110</id>
    <title>gsd-2019-17110</title>
    <updated>2026-10-09T19:14:07.370478+00:00</updated>
    <content>gsd-2019-17110</content>
    <link href="https://vulnerability.circl.lu/vuln/gsd-2019-17110"/>
  </entry>
</feed>
