CVE-2024-37891VulnerabilityPublished 13 Aug 2026Updated 12 Oct 2026

CVE-2024-37891: Gimme aws creds · urllib3's Proxy-Authorization request header isn't stripped during cross-origin redirects

Affects gimme-aws-credsSource GCVE Database

Not known to be exploited · CVSS 4.4 Medium : upgrade to 2.8.2_3 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.1% chance of exploitation in 30 days – higher than 66% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.29.0_1, 0.43.0_4, 1.28.0_1 +4

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
Homebrewlocust`pkg:brew/locust`Other threats	Affected >=2.2.1 <2.29.0_1	Fixed in 2.29.0_1
Homebrewtoot`pkg:brew/toot`Other threats	Affected >=0.26.0 <0.43.0_4	Fixed in 0.43.0_4
Homebrewggshield`pkg:brew/ggshield`Other threats	Affected >=1.19.1 <1.28.0_1	Fixed in 1.28.0_1
Homebrewrobot-framework`pkg:brew/robot-framework`Other threats	Affected <7.4.2_2	Fixed in 7.4.2_2
Homebrewparliament`pkg:brew/parliament`Other threats	Affected >=1.3.1 <1.6.2_3	Fixed in 1.6.2_3
Homebrewosc-cli`pkg:brew/osc-cli`Other threats	Affected >=1.6 <1.11.0_6	Fixed in 1.11.0_6
Homebrewgimme-aws-creds`pkg:brew/gimme-aws-creds`Other threats	Affected >=2.1.1 <2.8.2_3	Fixed in 2.8.2_3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released an official security update (RHSA-2024:4422) for fence-agents in Red Hat Enterprise Linux 9 and related variants to address CVE-2024-37891. Users should apply this update promptly following Red Hat's published guidance at https://access.redhat.com/articles/11258. No additional mitigation steps are indicated beyond applying the official patch.

Description

When using urllib3's proxy support with `ProxyManager`, the `Proxy-Authorization` header is only sent to the configured proxy, as expected. However, when sending HTTP requests *without* using urllib3's proxy support, it's possible to accidentally configure the `Proxy-Authorization` header even though it won't have any effect as the request is not using a forwarding proxy or a tunneling proxy. In those cases, urllib3 doesn't treat the `Proxy-Authorization` HTTP header as one carrying authentication material and thus doesn't strip the header on cross-origin redirects. Because this is a highly unlikely scenario, we believe the severity of this vulnerability is low for almost all users. Out of an abundance of caution urllib3 will automatically strip the `Proxy-Authorization` header during cross-origin redirects to avoid the small chance that users are doing this on accident. Users should use urllib3's proxy support or disable automatic redirects to achieve safe processing of the `Proxy-Authorization` header, but we still decided to strip the header by default in order to further protect users who aren't using the correct approach. ## Affected usages We believe the number of usages affected by this advisory is low. It requires all of the following to be true to be exploited: * Setting the `Proxy-Authorization` header without using urllib3's built-in proxy support. * Not disabling HTTP redirects. * Either not using an HTTPS origin server or for the proxy or target origin to redirect to a malicious origin. ## Remediation * Using the `Proxy-Authorization` header with urllib3's `ProxyManager`. * Disabling HTTP redirects using `redirects=False` when sending requests. * Not using the `Proxy-Authorization` header.

Impact

The vulnerability affects the security of remote power management scripts used in high-availability clusters, potentially allowing sensitive proxy-authorization headers to be leaked during cross-origin redirects. This could undermine the reliability and security of fencing operations that isolate failed or unreachable nodes in a cluster. The issue is rated as moderate severity by Red Hat Product Security.

Summary

The fence-agents packages, which provide scripts for remote power management in cluster environments on Red Hat Enterprise Linux 9 and its variants, are affected by CVE-2024-37891. This vulnerability is related to urllib3 improperly handling proxy-authorization headers during cross-origin redirects, which could lead to unintended exposure of credentials or related security issues in cluster fencing operations. Red Hat has released a security update (RHSA-2024:4422) to fix this issue. The advisory rates the impact as moderate and applies to multiple Red Hat Enterprise Linux 9 variants including AppStream, HighAvailability, and ResilientStorage.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Jul 2026, 01:31 UTC

WeaknessesCWE-669

Technical details

References

Community reviews

Related threats