Bug 2496771 (CVE-2026-9079) - CVE-2026-9079 libcurl: libcurl: Information disclosure due to failure to clear proxy authentication credentials
Summary: CVE-2026-9079 libcurl: libcurl: Information disclosure due to failure to clea...
Keywords:
Status: NEW
Alias: CVE-2026-9079
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2526418 2526421 2497473 2509775 2526416 2526417 2526419 2526420 2526422 2526423
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-03 07:02 UTC by OSIDB Bzimport
Modified: 2026-09-28 14:23 UTC (History)
39 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:56869 0 None None None 2026-08-19 13:28:39 UTC
Red Hat Product Errata RHSA-2026:69125 0 None None None 2026-09-21 06:14:34 UTC
Red Hat Product Errata RHSA-2026:72506 0 None None None 2026-09-28 14:23:55 UTC

Description OSIDB Bzimport 2026-07-03 07:02:13 UTC 
libcurl had a flaw that when instructed to clear proxy authentication
credentials which made it not do so, leaving the old credentials around to get
used for subsequent transfers that should not know nor use them.
Comment 4 errata-xmlrpc 2026-08-19 13:28:38 UTC 
This issue has been addressed in the following products:

  Red Hat JBoss Core Services 2.4.62.SP5

Via RHSA-2026:56869 https://access.redhat.com/errata/RHSA-2026:56869
Comment 5 Jon Orris 2026-09-21 06:14:32 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:69125 https://access.redhat.com/errata/RHSA-2026:69125
Comment 6 Jon Orris 2026-09-28 14:23:52 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10.0 Extended Update Support

Via RHSA-2026:72506 https://access.redhat.com/errata/RHSA-2026:72506
Note You need to log in before you can comment on or make changes to this bug.