<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vulnerability Spoiler Alert - apache/httpd</title>
    <link>https://spaceraccoon.github.io/vulnerability-spoiler-alert</link>
    <description>Vulnerability alerts for apache/httpd</description>
    <language>en-us</language>
    <lastBuildDate>Fri, 17 Apr 2026 01:52:35 GMT</lastBuildDate>
    <atom:link href="https://spaceraccoon.github.io/vulnerability-spoiler-alert/feed/apache-httpd.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>[HIGH] Improper Access Control / Authentication Bypass in apache/httpd</title>
      <link>https://github.com/spaceraccoon/vulnerability-spoiler-alert/issues/84</link>
      <guid isPermaLink="true">https://github.com/spaceraccoon/vulnerability-spoiler-alert/issues/84</guid>
      <pubDate>Wed, 18 Mar 2026 20:59:05 GMT</pubDate>
      <description>The original example configuration had &apos;Require all granted&apos; at the Directory level, which grants unauthenticated access to all users by default. The LimitExcept block only required authentication for non-GET/POST/OPTIONS methods, but the outer &apos;Require all granted&apos; could override authentication requirements depending on configuration context. The patch removes &apos;Require all granted&apos; and replaces the LimitExcept approach with a RequireAny block that properly requires either the correct HTTP method OR an authenticated admin user, ensuring write operations require authentication.</description>
      <category>high</category>
      <category>unverified</category>
    </item>
  </channel>
</rss>