<?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://vulnerability.circl.lu</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, 20 Oct 2026 09:58:03 +0000</lastBuildDate>
    <item>
      <title>BREW-apprise-CVE-2026-59180 — Apprise forwards configured auth headers across cross-origin HTTP redirects</title>
      <link>https://vulnerability.circl.lu/vuln/brew-apprise-cve-2026-59180</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: apprise&lt;/p&gt;
&lt;p&gt;# Summary&lt;/p&gt;
&lt;p&gt;Apprise&amp;#39;s HTTP-based notification plugins and its HTTP attachment / config loaders (`apprise/attachment/http.py`, `apprise/config/http.py`) follow HTTP 3xx redirects by default and **re-send the user-configured auth headers and query parameters on the redirected request**. If an operator-configured destination is later compromised (service takeover, malicious update), or an attacker holds a MITM position on an unprotected network path, that destination can return a `302 Location:` to an arbitrary host and Apprise forwards the user&amp;#39;s secret (`X-Gotify-Key`, `Authorization`, bearer tokens in query, custom `+Header=` values) to that cross-origin host. The attacker does **not** need to control the original Apprise URL — only the response from a destination the operator already trusts.&lt;/p&gt;
&lt;p&gt;This is the application-layer analogue of urllib3 [`GHSA-34jh-p97f-mpxf`](https://github.com/urllib3/urllib3/security/advisories/GHSA-34jh-p97f-mpxf) / `CVE-2026-44431` (&amp;#34;`Proxy-Authorization` forwarded across cross-origin redirect&amp;#34;).&lt;/p&gt;
&lt;p&gt;# Affected versions&lt;/p&gt;
&lt;p&gt;All releases up to and including `v1.10.0` (latest PyPI release as of filing, 2026-04-26). Fixed in v1.11.0 (released 2026-05-29), which includes [PR #1610](https://github.com/caronc/apprise/pull/1610) (merged 2026-05-16, commit 68c0aef218055e4586cf4605fd6b56358f5f462d).&lt;/p&gt;
&lt;p&gt;# Details&lt;/p&gt;
&lt;p&gt;`apprise/plugins/gotify.py` (pre-fix HEAD, lines 226-244, verbatim):&lt;/p&gt;
&lt;p&gt;```python
headers = {
    &amp;#34;User-Agent&amp;#34;: self.app_id,
    &amp;#34;Content-Type&amp;#34;: &amp;#34;applicatio…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: apprise&lt;/p&gt;
&lt;p&gt;# Summary&lt;/p&gt;
&lt;p&gt;Apprise&amp;#39;s HTTP-based notification plugins and its HTTP attachment / config loaders (`apprise/attachment/http.py`, `apprise/config/http.py`) follow HTTP 3xx redirects by default and **re-send the user-configured auth headers and query parameters on the redirected request**. If an operator-configured destination is later compromised (service takeover, malicious update), or an attacker holds a MITM position on an unprotected network path, that destination can return a `302 Location:` to an arbitrary host and Apprise forwards the user&amp;#39;s secret (`X-Gotify-Key`, `Authorization`, bearer tokens in query, custom `+Header=` values) to that cross-origin host. The attacker does **not** need to control the original Apprise URL — only the response from a destination the operator already trusts.&lt;/p&gt;
&lt;p&gt;This is the application-layer analogue of urllib3 [`GHSA-34jh-p97f-mpxf`](https://github.com/urllib3/urllib3/security/advisories/GHSA-34jh-p97f-mpxf) / `CVE-2026-44431` (&amp;#34;`Proxy-Authorization` forwarded across cross-origin redirect&amp;#34;).&lt;/p&gt;
&lt;p&gt;# Affected versions&lt;/p&gt;
&lt;p&gt;All releases up to and including `v1.10.0` (latest PyPI release as of filing, 2026-04-26). Fixed in v1.11.0 (released 2026-05-29), which includes [PR #1610](https://github.com/caronc/apprise/pull/1610) (merged 2026-05-16, commit 68c0aef218055e4586cf4605fd6b56358f5f462d).&lt;/p&gt;
&lt;p&gt;# Details&lt;/p&gt;
&lt;p&gt;`apprise/plugins/gotify.py` (pre-fix HEAD, lines 226-244, verbatim):&lt;/p&gt;
&lt;p&gt;```python
headers = {
    &amp;#34;User-Agent&amp;#34;: self.app_id,
    &amp;#34;Content-Type&amp;#34;: &amp;#34;applicatio…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/brew-apprise-cve-2026-59180</guid>
    </item>
    <item>
      <title>CVE-2026-59180 — Apprise forwards configured auth headers across cross-origin HTTP redirects</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-59180</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; caronc apprise&lt;/p&gt;
&lt;p&gt;Apprise is an open source library which allows you to send a notification to almost all of the most popular notification services available. Prior to 1.11.0, Apprise HTTP-based notification plugins and HTTP attachment and config loaders in apprise/attachment/http.py and apprise/config/http.py follow HTTP redirects by default and resend user-configured auth headers and query parameters on the redirected request, allowing a compromised trusted destination or on-path attacker to receive secrets such as Authorization headers, bearer tokens, custom headers, and service keys. This issue is fixed in version 1.11.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; caronc apprise&lt;/p&gt;
&lt;p&gt;Apprise is an open source library which allows you to send a notification to almost all of the most popular notification services available. Prior to 1.11.0, Apprise HTTP-based notification plugins and HTTP attachment and config loaders in apprise/attachment/http.py and apprise/config/http.py follow HTTP redirects by default and resend user-configured auth headers and query parameters on the redirected request, allowing a compromised trusted destination or on-path attacker to receive secrets such as Authorization headers, bearer tokens, custom headers, and service keys. This issue is fixed in version 1.11.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-59180</guid>
    </item>
    <item>
      <title>GHSA-856c-92hv-3vxx — Apprise forwards configured auth headers across cross-origin HTTP redirects</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-856c-92hv-3vxx</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: apprise&lt;/p&gt;
&lt;p&gt;# Summary&lt;/p&gt;
&lt;p&gt;Apprise&amp;#39;s HTTP-based notification plugins and its HTTP attachment / config loaders (`apprise/attachment/http.py`, `apprise/config/http.py`) follow HTTP 3xx redirects by default and **re-send the user-configured auth headers and query parameters on the redirected request**. If an operator-configured destination is later compromised (service takeover, malicious update), or an attacker holds a MITM position on an unprotected network path, that destination can return a `302 Location:` to an arbitrary host and Apprise forwards the user&amp;#39;s secret (`X-Gotify-Key`, `Authorization`, bearer tokens in query, custom `+Header=` values) to that cross-origin host. The attacker does **not** need to control the original Apprise URL — only the response from a destination the operator already trusts.&lt;/p&gt;
&lt;p&gt;This is the application-layer analogue of urllib3 [`GHSA-34jh-p97f-mpxf`](https://github.com/urllib3/urllib3/security/advisories/GHSA-34jh-p97f-mpxf) / `CVE-2026-44431` (&amp;#34;`Proxy-Authorization` forwarded across cross-origin redirect&amp;#34;).&lt;/p&gt;
&lt;p&gt;# Affected versions&lt;/p&gt;
&lt;p&gt;All releases up to and including `v1.10.0` (latest PyPI release as of filing, 2026-04-26). Fixed in v1.11.0 (released 2026-05-29), which includes [PR #1610](https://github.com/caronc/apprise/pull/1610) (merged 2026-05-16, commit 68c0aef218055e4586cf4605fd6b56358f5f462d).&lt;/p&gt;
&lt;p&gt;# Details&lt;/p&gt;
&lt;p&gt;`apprise/plugins/gotify.py` (pre-fix HEAD, lines 226-244, verbatim):&lt;/p&gt;
&lt;p&gt;```python
headers = {
    &amp;#34;User-Agent&amp;#34;: self.app_id,
    &amp;#34;Content-Type&amp;#34;: &amp;#34;applicatio…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: apprise&lt;/p&gt;
&lt;p&gt;# Summary&lt;/p&gt;
&lt;p&gt;Apprise&amp;#39;s HTTP-based notification plugins and its HTTP attachment / config loaders (`apprise/attachment/http.py`, `apprise/config/http.py`) follow HTTP 3xx redirects by default and **re-send the user-configured auth headers and query parameters on the redirected request**. If an operator-configured destination is later compromised (service takeover, malicious update), or an attacker holds a MITM position on an unprotected network path, that destination can return a `302 Location:` to an arbitrary host and Apprise forwards the user&amp;#39;s secret (`X-Gotify-Key`, `Authorization`, bearer tokens in query, custom `+Header=` values) to that cross-origin host. The attacker does **not** need to control the original Apprise URL — only the response from a destination the operator already trusts.&lt;/p&gt;
&lt;p&gt;This is the application-layer analogue of urllib3 [`GHSA-34jh-p97f-mpxf`](https://github.com/urllib3/urllib3/security/advisories/GHSA-34jh-p97f-mpxf) / `CVE-2026-44431` (&amp;#34;`Proxy-Authorization` forwarded across cross-origin redirect&amp;#34;).&lt;/p&gt;
&lt;p&gt;# Affected versions&lt;/p&gt;
&lt;p&gt;All releases up to and including `v1.10.0` (latest PyPI release as of filing, 2026-04-26). Fixed in v1.11.0 (released 2026-05-29), which includes [PR #1610](https://github.com/caronc/apprise/pull/1610) (merged 2026-05-16, commit 68c0aef218055e4586cf4605fd6b56358f5f462d).&lt;/p&gt;
&lt;p&gt;# Details&lt;/p&gt;
&lt;p&gt;`apprise/plugins/gotify.py` (pre-fix HEAD, lines 226-244, verbatim):&lt;/p&gt;
&lt;p&gt;```python
headers = {
    &amp;#34;User-Agent&amp;#34;: self.app_id,
    &amp;#34;Content-Type&amp;#34;: &amp;#34;applicatio…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-856c-92hv-3vxx</guid>
    </item>
  </channel>
</rss>
