VulnerabilityPublished 28 Jan 2026

CVE-2025-14840: Drupal HTTP Client Manager · Unchecked Error Condition

Affects Drupal HTTP Client ManagerSource CVE Database V5

Not known to be exploited · CVSS 7.5 High · fixed in 11.0.1 : patch Drupal HTTP Client Manager soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 11.0.1, 10.0.2, 9.3.13

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

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

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: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Jan 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 26 Oct 2026.

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 or the CVSS exploit maturity 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 Drupal HTTP Client Manager to 11.0.1, 10.0.2 or 9.3.13.

Affected software

Product	Affected	Fixed in
DrupalHTTP Client Manager	Affected >=11.0.0 <11.0.1	Fixed in 11.0.1
DrupalHTTP Client Manager	Affected >=10.0.0 <10.0.2	Fixed in 10.0.2
DrupalHTTP Client Manager	Affected <9.3.13	Fixed in 9.3.13
Packagistdrupal/http_client_manager`pkg:composer/drupal/http_client_manager`Other threats	Affected =0.0.0 =10.0.0 =11.0.0	Fixed in–

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

AI-suggested

Immediately identify and inventory all Drupal installations using affected HTTP Client Manager versions (prior to 9.3.13, 10.0.2, and 11.0.1).
3. If you cannot patch yet, implement network-level protections such as web application firewalls (WAFs) to detect and block abnormal HTTP client requests that may trigger the vulnerability. 4. Review and harden HTTP Client Manager configurations to limit exposure to untrusted inputs and reduce the attack surface. 5. Monitor web server and application logs for unusual HTTP client activity or error patterns indicative of exploitation attempts. 6. Conduct internal security assessments and penetration testing focused on HTTP client handling to identify potential weaknesses. 7. Educate development and operations teams about the importance of proper error and exception handling in HTTP client components. 8. Establish incident response plans to quickly address potential denial of service incidents related to this vulnerability.

Description

CVE-2025-14840 is a high-severity vulnerability in the Drupal HTTP Client Manager affecting versions prior to 9.3.13, 10.0.2, and 11.0.1. It stems from an improper check for unusual or exceptional conditions (CWE-754), enabling forceful browsing attacks. The vulnerability allows unauthenticated, remote attackers to cause a denial of service by exploiting the HTTP Client Manager's failure to handle exceptional conditions properly. There are no known exploits in the wild yet.

Impact

For European organizations, the impact of CVE-2025-14840 can be substantial, particularly for those relying on Drupal for public-facing websites, intranets, or critical business applications. The vulnerability enables remote attackers to cause denial of service, potentially leading to website downtime, service disruption, and loss of availability for end-users. This can affect customer trust, operational continuity, and compliance with service-level agreements. Sectors such as government, finance, healthcare, and e-commerce, which often use Drupal for content management, may face increased risk due to the critical nature of their services. Additionally, disruption of public sector websites or portals could have broader societal impacts. While confidentiality and integrity are not directly compromised, the availability impact alone can cause significant operational and reputational damage. The absence of known exploits currently provides a window for proactive mitigation before widespread exploitation occurs.

CWE-754Improper Check for Unusual or Exceptional Conditions (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
Check the results of all functions that return a value and verify that the value is expected.
Implementation
If using exception handling, catch and throw specific exceptions instead of overly-general exceptions (CWE-396, CWE-397). Catch and handle exceptions as locally as possible so that exceptions do not propagate too far up the call stack (CWE-705). Avoid unchecked or uncaught exceptions where feasible (CWE-248).
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.7 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

drupal.org/sa-contrib-2025-126 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Feb 2026, 09:01 UTC

WeaknessesCWE-754

Technical details

References

Community reviews

Related threats