
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Shellvoide Blog - AI-Powered Cybersecurity, Compliance &amp; Penetration Testing</title>
      <link>https://shellvoide.com/blog/blog</link>
      <description>The Shellvoide security blog: AI-driven penetration testing, vulnerability research, and application security insights from the team behind KLUE.</description>
      <language>en-us</language>
      <managingEditor>info@shellvoide.com (Shellvoide)</managingEditor>
      <webMaster>info@shellvoide.com (Shellvoide)</webMaster>
      <lastBuildDate>Fri, 23 Oct 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://shellvoide.com/blog/tags/information-disclosure/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://shellvoide.com/blog/blog/follow-redirects-credential-header-leaks</guid>
    <title>Two Information-Disclosure CVEs in follow-redirects: CVE-2026-111756 and CVE-2026-111755</title>
    <link>https://shellvoide.com/blog/blog/follow-redirects-credential-header-leaks</link>
    <description>follow-redirects is the redirect-following layer under axios and a large part of the Node HTTP ecosystem. We found two separate ways its cross-origin credential-header stripping control fails silently, one through a type assumption that the header container is always a plain object, and one through an incomplete regular-expression escaper. Both break the protection introduced to fix prior CVEs. Both were reported, accepted, assigned CVEs (CVE-2026-111756 and CVE-2026-111755), and fixed in 1.16.1.</description>
    <pubDate>Fri, 23 Oct 2026 00:00:00 GMT</pubDate>
    <author>info@shellvoide.com (Shellvoide)</author>
    <category>klue</category><category>case-study</category><category>vulnerability-research</category><category>information-disclosure</category><category>credential-leak</category><category>javascript</category><category>nodejs</category><category>follow-redirects</category><category>axios</category><category>http-client</category><category>api-security</category><category>autonomous-security</category><category>appsec</category>
  </item>

    </channel>
  </rss>
