Information Exposure Affecting jbcs-httpd24-libcurl-devel package, versions *


Severity

Recommended
low

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.29% (21st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-JBCSHTTPD24LIBCURLDEVEL-20944551
  • published15 Oct 2026
  • disclosed14 Oct 2026

Introduced: 14 Oct 2026

NewCVE-2026-86414  (opens in a new tab)
CWE-201  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:10 jbcs-httpd24-libcurl-devel.

NVD Description

Note: Versions mentioned in the description apply only to the upstream jbcs-httpd24-libcurl-devel package and not the jbcs-httpd24-libcurl-devel package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

An HTTP proxy can trick libcurl into sending the origin's credentials (Basic password, or a Negotiate/Kerberos ticket) to the proxy itself, by answering the CONNECT tunnel request with 401 WWW-Authenticate: instead of the expected 407 Proxy-Authenticate:.

CVSS Base Scores

version 3.1