<?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-09T17:03:04.900977+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/bdu:2025-10836</id>
    <title>bdu:2025-10836</title>
    <updated>2026-10-09T17:03:06.995809+00:00</updated>
    <content>bdu:2025-10836</content>
    <link href="https://vulnerability.circl.lu/vuln/bdu:2025-10836"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/bit-vault-2024-5798</id>
    <title>BIT-vault-2024-5798 — Vault Incorrectly Validated JSON Web Tokens (JWT) Audience Claims</title>
    <updated>2026-10-09T17:03:06.995865+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 did not properly validate the JSON Web Token (JWT) role-bound audience claim when using the Vault JWT auth method. This may have resulted in Vault validating a JWT the audience and role-bound claims do not match, allowing an invalid login to succeed when it should have been rejected.</p>
<p>This vulnerability, CVE-2024-5798, was fixed in Vault and Vault Enterprise 1.17.0, 1.16.3, and 1.15.9</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/bit-vault-2024-5798"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2024-5798</id>
    <title>fkie_cve-2024-5798</title>
    <updated>2026-10-09T17:03:06.995926+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>Vault and Vault Enterprise did not properly validate the JSON Web Token (JWT) role-bound audience claim when using the Vault JWT auth method. This may have resulted in Vault validating a JWT the audience and role-bound claims do not match, allowing an invalid login to succeed when it should have been rejected.</p>
<p>This vulnerability, CVE-2024-5798, was fixed in Vault and Vault Enterprise 1.17.0, 1.16.3, and 1.15.9</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2024-5798"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-32cj-5wx4-gq8p</id>
    <title>GHSA-32cj-5wx4-gq8p — HashiCorp Vault Incorrectly Validated JSON Web Tokens (JWT) Audience Claims</title>
    <updated>2026-10-09T17:03:06.995971+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 did not properly validate the JSON Web Token (JWT) role-bound audience claim when using the Vault JWT auth method. This may have resulted in Vault validating a JWT the audience and role-bound claims do not match, allowing an invalid login to succeed when it should have been rejected.</p>
<p>This vulnerability, CVE-2024-5798, was fixed in Vault and Vault Enterprise 1.17.0, 1.16.3, and 1.15.9</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-32cj-5wx4-gq8p"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/wid-sec-w-2024-1365</id>
    <title>WID-SEC-W-2024-1365 — Hashicorp Vault: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen</title>
    <updated>2026-10-09T17:03:06.996015+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter Angreifer mit hohen Privilegien kann eine Schwachstelle in Hashicorp Vault ausnutzen, um Sicherheitsvorkehrungen zu umgehen.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/wid-sec-w-2024-1365"/>
  </entry>
</feed>
