<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Responsible-Disclosure on anir0y // infosec blog</title>
    <link>https://blogs.anir0y.in/tags/responsible-disclosure/</link>
    <description>Recent content in Responsible-Disclosure on anir0y // infosec blog</description>
    <image>
      <title>anir0y // infosec blog</title>
      <url>https://blogs.anir0y.in/images/og-default.png</url>
      <link>https://blogs.anir0y.in/images/og-default.png</link>
    </image>
    <generator>Hugo -- 0.155.0</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 15 Nov 2026 10:30:00 +0530</lastBuildDate>
    <atom:link href="https://blogs.anir0y.in/tags/responsible-disclosure/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Your Wazuh 5.0 RC Dashboard Is Printing Its API Password on the Login Page</title>
      <link>https://blogs.anir0y.in/posts/2026-11-15-wazuh-dashboard-login-credential-leak/</link>
      <pubDate>Sun, 15 Nov 2026 10:30:00 +0530</pubDate>
      <guid>https://blogs.anir0y.in/posts/2026-11-15-wazuh-dashboard-login-credential-leak/</guid>
      <description>Wazuh 5.0.0-rc1 ships an OpenSearch Dashboards build whose rendering service injects each plugin&amp;#39;s full server config — including the wazuh-wui API password and keystore secrets — into the unauthenticated login page. Here is the root cause, how to check your own instance, and why it is a silent fix with no CVE.</description>
    </item>
  </channel>
</rss>
