<?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://db.gcve.eu</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, 17 Nov 2026 15:32:47 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-79779 — rclone before v1.75.0 WebDAV Credential Exposure via HTTPS-to-HTTP Redirect</title>
      <link>https://db.gcve.eu/vuln/cve-2026-79779</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; rclone&lt;/p&gt;
&lt;p&gt;rclone versions before v1.75.0 fail to reject transport downgrades in redirect handling, allowing Basic authorization and Cookie headers to be replayed over plaintext HTTP after same-host HTTPS-to-HTTP redirects. An on-path attacker observing the plaintext hop can capture and reuse credentials to perform WebDAV operations with the compromised account&amp;#39;s permissions.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; rclone&lt;/p&gt;
&lt;p&gt;rclone versions before v1.75.0 fail to reject transport downgrades in redirect handling, allowing Basic authorization and Cookie headers to be replayed over plaintext HTTP after same-host HTTPS-to-HTTP redirects. An on-path attacker observing the plaintext hop can capture and reuse credentials to perform WebDAV operations with the compromised account&amp;#39;s permissions.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-79779</guid>
    </item>
    <item>
      <title>GHSA-h4mf-4v27-hggj — rclone: WebDAV Credentials Survive a Same-Host HTTPS-to-HTTP Redirect</title>
      <link>https://db.gcve.eu/vuln/ghsa-h4mf-4v27-hggj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/rclone/rclone&lt;/p&gt;
&lt;p&gt;## 1. Summary&lt;/p&gt;
&lt;p&gt;WebDAV&amp;#39;s default redirect handling can replay Basic authorization and configured Cookie headers over plaintext HTTP after a same-host HTTPS-to-HTTP redirect. This was reproduced through the real backend. Unlike the low-impact STS token in rclone&amp;#39;s published S3 redirect advisory, Basic passwords and session cookies are complete reusable credentials, supporting a High rating when they grant normal WebDAV read/write access.&lt;/p&gt;
&lt;p&gt;The credible threat requires a legitimate endpoint, gateway, or accelerator to emit an unsafe redirect and an adjacent/on-path actor to observe the plaintext hop. A report should not rely on a malicious original WebDAV endpoint because that endpoint already receives the credentials.&lt;/p&gt;
&lt;p&gt;## 2. Affected Assets &amp;amp; Attack Surface&lt;/p&gt;
&lt;p&gt;- Backend configuration/authentication: `backend/webdav/webdav.go:127-139`, `170-206`, `440-530`
- Shared redirect callback: `lib/rest/rest.go:218-231`
- HTTP client: `fs/fshttp/http.go:311-329`
- Credentials: Basic passwords, bearer authorization, SharePoint/session cookies, and configured secret headers
- Confirmed affected version: `&amp;lt;= v1.74.0-240`&lt;/p&gt;
&lt;p&gt;## 3. Technical Root Cause Analysis&lt;/p&gt;
&lt;p&gt;`PreserveMethodRedirectFn` limits redirect count and restores the original method, but it does not reject a transport downgrade or compare the full origin tuple. The client therefore relies on Go&amp;#39;s hostname-oriented sensitive-header forwarding rules. Those rules can preserve `Authorization` and Cookie on a same-host redirect even when the…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/rclone/rclone&lt;/p&gt;
&lt;p&gt;## 1. Summary&lt;/p&gt;
&lt;p&gt;WebDAV&amp;#39;s default redirect handling can replay Basic authorization and configured Cookie headers over plaintext HTTP after a same-host HTTPS-to-HTTP redirect. This was reproduced through the real backend. Unlike the low-impact STS token in rclone&amp;#39;s published S3 redirect advisory, Basic passwords and session cookies are complete reusable credentials, supporting a High rating when they grant normal WebDAV read/write access.&lt;/p&gt;
&lt;p&gt;The credible threat requires a legitimate endpoint, gateway, or accelerator to emit an unsafe redirect and an adjacent/on-path actor to observe the plaintext hop. A report should not rely on a malicious original WebDAV endpoint because that endpoint already receives the credentials.&lt;/p&gt;
&lt;p&gt;## 2. Affected Assets &amp;amp; Attack Surface&lt;/p&gt;
&lt;p&gt;- Backend configuration/authentication: `backend/webdav/webdav.go:127-139`, `170-206`, `440-530`
- Shared redirect callback: `lib/rest/rest.go:218-231`
- HTTP client: `fs/fshttp/http.go:311-329`
- Credentials: Basic passwords, bearer authorization, SharePoint/session cookies, and configured secret headers
- Confirmed affected version: `&amp;lt;= v1.74.0-240`&lt;/p&gt;
&lt;p&gt;## 3. Technical Root Cause Analysis&lt;/p&gt;
&lt;p&gt;`PreserveMethodRedirectFn` limits redirect count and restores the original method, but it does not reject a transport downgrade or compare the full origin tuple. The client therefore relies on Go&amp;#39;s hostname-oriented sensitive-header forwarding rules. Those rules can preserve `Authorization` and Cookie on a same-host redirect even when the…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-h4mf-4v27-hggj</guid>
    </item>
  </channel>
</rss>
