<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vulnerability Spoiler Alert - hashicorp/vault</title>
    <link>https://spaceraccoon.github.io/vulnerability-spoiler-alert</link>
    <description>Vulnerability alerts for hashicorp/vault</description>
    <language>en-us</language>
    <lastBuildDate>Tue, 11 Aug 2026 21:01:38 GMT</lastBuildDate>
    <atom:link href="https://spaceraccoon.github.io/vulnerability-spoiler-alert/feed/hashicorp-vault.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>[HIGH] SQL Injection in hashicorp/vault</title>
      <link>https://github.com/spaceraccoon/vulnerability-spoiler-alert/issues/371</link>
      <guid isPermaLink="true">https://github.com/spaceraccoon/vulnerability-spoiler-alert/issues/371</guid>
      <pubDate>Wed, 05 Aug 2026 09:52:39 GMT</pubDate>
      <description>The DisplayName field, which is user/token controlled (e.g., from token display names or OIDC/JWT claims), was passed unsanitized into database username templates used to generate credentials, allowing SQL metacharacters or malicious payloads to be injected into generated usernames sent to the database. The patch adds sanitizeDisplayName to strip all characters except alphanumerics, hyphens, and underscores before using DisplayName in the credential generation request, and adds a warning for username_template usage without truncation.</description>
      <category>high</category>
      <category>verified</category>
      
    </item>
  </channel>
</rss>