<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 03:55:02 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-275783</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-275783</link>
      <description>EUVD-2026-275783</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-275783</guid>
    </item>
    <item>
      <title>fkie_cve-2026-32136</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-32136</link>
      <description>&lt;p&gt;AdGuard Home is a network-wide software for blocking ads and tracking. Prior to 0.107.73, an unauthenticated remote attacker can bypass all authentication in AdGuardHome by sending an HTTP/1.1 request that requests an upgrade to HTTP/2 cleartext (h2c). Once the upgrade is accepted, the resulting HTTP/2 connection is handled by the inner mux, which has no authentication middleware attached. All subsequent HTTP/2 requests on that connection are processed as fully authenticated, regardless of whether any credentials were provided. This vulnerability is fixed in 0.107.73.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;AdGuard Home is a network-wide software for blocking ads and tracking. Prior to 0.107.73, an unauthenticated remote attacker can bypass all authentication in AdGuardHome by sending an HTTP/1.1 request that requests an upgrade to HTTP/2 cleartext (h2c). Once the upgrade is accepted, the resulting HTTP/2 connection is handled by the inner mux, which has no authentication middleware attached. All subsequent HTTP/2 requests on that connection are processed as fully authenticated, regardless of whether any credentials were provided. This vulnerability is fixed in 0.107.73.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-32136</guid>
    </item>
    <item>
      <title>GHSA-5fg6-wrq4-w5gh — AdGuard Home: HTTP/2 Cleartext (h2c) Upgrade Authentication Bypass</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5fg6-wrq4-w5gh</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/AdguardTeam/AdGuardHome&lt;/p&gt;
&lt;p&gt;VULNERABILITY: HTTP/2 Cleartext (h2c) Upgrade Authentication Bypass
========================================================================
Severity:  CRITICAL
CVSS 3.1:  9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
CWE:       CWE-287 (Improper Authentication)
Component: internal/home/web.go
Affected:  AdGuardHome (tested on v0.107.72)&lt;/p&gt;
&lt;p&gt;------------------------------------------------------------------------
Summary
------------------------------------------------------------------------&lt;/p&gt;
&lt;p&gt;An unauthenticated remote attacker can bypass all authentication in AdGuardHome by sending an HTTP/1.1 request that requests an upgrade to HTTP/2 cleartext (h2c). Once the upgrade is accepted, the resulting HTTP/2 connection is handled by the inner mux, which has no authentication middleware attached. All subsequent HTTP/2 requests on that connection are processed as fully authenticated, regardless of whether any credentials were provided.&lt;/p&gt;
&lt;p&gt;------------------------------------------------------------------------
Root Cause
------------------------------------------------------------------------&lt;/p&gt;
&lt;p&gt;In internal/home/web.go (approximately lines 268-283), the HTTP server is constructed as follows:
    hdlr := h2c.NewHandler(
        withMiddlewares(web.conf.mux, limitRequestBody),  // no auth
        &amp;amp;http2.Server{},
    )
    web.httpServer = &amp;amp;http.Server{
        Handler: web.auth.middleware().Wrap(hdlr),        // auth here
    }&lt;/p&gt;
&lt;p&gt;The authentication middleware wraps the h2c handler at the outer…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/AdguardTeam/AdGuardHome&lt;/p&gt;
&lt;p&gt;VULNERABILITY: HTTP/2 Cleartext (h2c) Upgrade Authentication Bypass
========================================================================
Severity:  CRITICAL
CVSS 3.1:  9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
CWE:       CWE-287 (Improper Authentication)
Component: internal/home/web.go
Affected:  AdGuardHome (tested on v0.107.72)&lt;/p&gt;
&lt;p&gt;------------------------------------------------------------------------
Summary
------------------------------------------------------------------------&lt;/p&gt;
&lt;p&gt;An unauthenticated remote attacker can bypass all authentication in AdGuardHome by sending an HTTP/1.1 request that requests an upgrade to HTTP/2 cleartext (h2c). Once the upgrade is accepted, the resulting HTTP/2 connection is handled by the inner mux, which has no authentication middleware attached. All subsequent HTTP/2 requests on that connection are processed as fully authenticated, regardless of whether any credentials were provided.&lt;/p&gt;
&lt;p&gt;------------------------------------------------------------------------
Root Cause
------------------------------------------------------------------------&lt;/p&gt;
&lt;p&gt;In internal/home/web.go (approximately lines 268-283), the HTTP server is constructed as follows:
    hdlr := h2c.NewHandler(
        withMiddlewares(web.conf.mux, limitRequestBody),  // no auth
        &amp;amp;http2.Server{},
    )
    web.httpServer = &amp;amp;http.Server{
        Handler: web.auth.middleware().Wrap(hdlr),        // auth here
    }&lt;/p&gt;
&lt;p&gt;The authentication middleware wraps the h2c handler at the outer…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5fg6-wrq4-w5gh</guid>
    </item>
  </channel>
</rss>
