<?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-02T10:02:11.977341+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:2025-09561</id>
    <title>bdu:2025-09561</title>
    <updated>2026-10-02T10:02:11.982027+00:00</updated>
    <content>bdu:2025-09561</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2025-09561"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bit-vault-2025-6037</id>
    <title>BIT-vault-2025-6037 — Vault Certificate Auth Method Did Not Validate Common Name For Non-CA Certificates</title>
    <updated>2026-10-02T10:02:11.982059+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: vault</p>
<p>Vault and Vault Enterprise (“Vault”) TLS certificate auth method did not correctly validate client certificates when configured with a non-CA certificate as [+trusted certificate+|https://developer.hashicorp.com/vault/api-docs/auth/cert#certificate]. In this configuration, an attacker may be able to craft a malicious certificate that could be used to impersonate another user. Fixed in Vault Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-vault-2025-6037"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-272561</id>
    <title>EUVD-2026-272561</title>
    <updated>2026-10-02T10:02:11.982096+00:00</updated>
    <content>EUVD-2026-272561</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-272561"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-6037</id>
    <title>fkie_cve-2025-6037</title>
    <updated>2026-10-02T10:02:11.982110+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Vault and Vault Enterprise (“Vault”) TLS certificate auth method did not correctly validate client certificates when configured with a non-CA certificate as [+trusted certificate+|https://developer.hashicorp.com/vault/api-docs/auth/cert#certificate]. In this configuration, an attacker may be able to craft a malicious certificate that could be used to impersonate another user. Fixed in Vault Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-6037"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-6c5r-4wfc-3mcx</id>
    <title>GHSA-6c5r-4wfc-3mcx — Hashicorp Vault has Incorrect Validation for Non-CA Certificates</title>
    <updated>2026-10-02T10:02:11.982134+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/hashicorp/vault</p>
<p>Vault and Vault Enterprise (“Vault”) TLS certificate auth method did not correctly validate client certificates when configured with a non-CA certificate as [+trusted certificate+|https://developer.hashicorp.com/vault/api-docs/auth/cert#certificate]. In this configuration, an attacker may be able to craft a malicious certificate that could be used to impersonate another user. Fixed in Vault Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-6c5r-4wfc-3mcx"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2025:15434-1</id>
    <title>openSUSE-SU-2025:15434-1 — govulncheck-vulndb-0.0.20250811T192933-1.1 on GA media</title>
    <updated>2026-10-02T10:02:11.982157+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>govulncheck-vulndb-0.0.20250811T192933-1.1 on GA media</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2025:15434-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1702</id>
    <title>WID-SEC-W-2025-1702 — Hashicorp Vault Community und Enterprise: Mehrere Schwachstellen</title>
    <updated>2026-10-02T10:02:11.982181+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in Hashicorp Vault ausnutzen, um erhöhte Rechte zu erlangen, Sicherheitsmaßnahmen zu umgehen, beliebigen Code auszuführen und vertrauliche Informationen preiszugeben.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1702"/>
  </entry>
</feed>
