HTTP Client Manager - Less critical - Information disclosure - SA-CONTRIB-2025-126

published 2025-12-17 10 mo ago modified 2026-09-10 1 mo ago also DRUPAL-CONTRIB-2025-126 , EUVD-2025-206433

cvss: 7.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 24%
public exploits: 0; none known

Improper Check for Unusual or Exceptional Conditions vulnerability in Drupal HTTP Client Manager allows Forceful Browsing.This issue affects HTTP Client Manager: from 0.0.0 before 9.3.13, from 10.0.0 before 10.0.2, from 11.0.0 before 11.0.1.

Patch / fix

fixed in 2

packagist drupal/http_client_manager 9.3.13, 10.0.2, 11.0.1
Drupal HTTP Client Manager 9.3.13, 10.0.2, 11.0.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-14840 updated 2026-06-26 cvss 2.2

drupal: Drupal Http Client Manager: Information disclosure due to insufficient data separation

Red Hat All currently supported Red Hat products
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 9 mo ago (2026-01-29)

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CISA ADP	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem	package	affected	fixed in
packagist	drupal/http_client_manager	<9.3.13 >=10.0.0, <10.0.2 >=11.0.0, <11.0.1	9.3.13 10.0.2 11.0.1

Affected products

Drupal HTTP Client Manager

Classification

Weakness

CWE-754 Improper Check for Unusual or Exceptional Conditions

References

drupal.org /sa-contrib-2025-126
vendor-advisory, web

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary