EUVD-2026-42940Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
AC:H reflects the requirement for on-path position or compromised destination; C:L because leaked credentials are scoped to configured service keys, not system-wide data.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
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.
AnalysisAI
HTTP redirect handling in Apprise prior to 1.11.0 leaks user-configured secrets - including Authorization headers, bearer tokens, custom headers, and service API keys - by blindly resending them on redirected requests to attacker-controlled endpoints. Any deployment using Apprise's HTTP-based notification plugins or its HTTP attachment and config loaders (apprise/attachment/http.py, apprise/config/http.py) is affected. An on-path attacker or a compromised notification destination can silently harvest these credentials. No public exploit has been identified at time of analysis, and EPSS data is not present in the source intel, but the credential-theft impact on third-party service integrations elevates real-world risk above the Low CVSS score suggests.
Technical ContextAI
Apprise (CPE: cpe:2.3:a:caronc:apprise:*:*:*:*:*:*:*:*) is an open-source Python notification aggregation library that supports dozens of third-party services via HTTP. Its HTTP-based plugin architecture, along with attachment and configuration loaders, uses Python's requests library (or equivalent) to make outbound HTTP calls. The root cause is CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor): when an HTTP 3xx redirect is received, Apprise follows it without stripping sensitive request metadata - specifically Authorization headers, bearer tokens, custom headers, and query parameters containing service keys. This violates RFC 7235 guidance that sensitive credentials should not be forwarded across redirect boundaries to potentially different origins. The affected files are apprise/attachment/http.py and apprise/config/http.py, indicating the flaw is present in both data-loading code paths and the core notification dispatch path.
RemediationAI
Upgrade Apprise to version 1.11.0 or later; this is the vendor-confirmed fix (commit 68c0aef218055e4586cf4605fd6b56358f5f462d, PR #1610) available at https://github.com/caronc/apprise/releases/tag/v1.11.0. Run 'pip install --upgrade apprise>=1.11.0' or update the pinned version in your requirements file. If upgrading is not immediately feasible, the primary compensating control is to audit all configured HTTP notification endpoints, attachment sources, and remote config URLs to ensure they are fully trusted, internally hosted, and not subject to third-party redirect chains - removing any externally hosted endpoints until patching is complete. Additionally, rotate any credentials (API keys, bearer tokens, Authorization headers) that were in use with Apprise's HTTP plugins, since there is no way to confirm retrospectively whether a redirect-based credential harvest occurred. Restricting network egress from the host running Apprise to only explicitly whitelisted destination IPs reduces on-path interception risk but does not address the compromised-destination vector.
Same weakness CWE-200 – Information Exposure
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today