CVE-2026-8368

LWP::UserAgent versions before 6.83 for Perl leak Authorization and Proxy-Authorization headers on cross-origin redirects

CVE-2026-8368 is fixed in 3 products on 1 platform, first by libwww-perl 6.61-1ubuntu0.1, released May 12, 2026. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
6.5
Moderate
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0027
18th percentile

LWP::UserAgent versions before 6.83 for Perl leak Authorization and Proxy-Authorization headers on cross-origin redirects. On a 3xx response, the redirect handler strips only Host and Cookie before issuing the follow-up request. Caller-supplied Authorization and Proxy-Authorization headers are sent unchanged to the redirect target, including across scheme, host, or port changes. A redirect to an attacker controlled host therefore discloses the caller's credentials to that host.

Where it's fixed

ProductFixed inFixReleased
Linux
libwww-perl · Debian 14 6.83-1 DEBIAN-CVE-2026-8368 May 27, 2026
libwww-perl · Ubuntu 22.04.1 LTS (jammy) 6.61-1ubuntu0.1 libwww-perl 6.61-1ubuntu0.1 May 12, 2026
libwww-perl · Ubuntu 24.04.5 LTS (noble) 6.76-1ubuntu0.1 libwww-perl 6.76-1ubuntu0.1 May 12, 2026
libwww-perl · Ubuntu 25.10 (questing) 6.78-1ubuntu0.1 libwww-perl 6.78-1ubuntu0.1 May 12, 2026
libwww-perl · Ubuntu 26.04.1 LTS (resolute) 6.81-1ubuntu0.1 libwww-perl 6.81-1ubuntu0.1 May 12, 2026
perl-libwww-perl · amzn 2023 6.58-1.amzn2023.0.3 ALAS2023-2026-1764 May 25, 2026
perl-libwww-perl · opensuse-leap 16.0 6.770.0-160000.3.1 OPENSUSE-SU-2026:21045-1 Jun 24, 2026
perl-libwww-perl · sles 15.7 6.31-150000.3.3.1 SUSE-SU-2026:2962-1 Jul 14, 2026
perl-libwww-perl · sles 16.0 6.770.0-160000.3.1 SUSE-SU-2026:22353-1 Jun 24, 2026
perl-libwww-perl-tests · amzn 2023 6.58-1.amzn2023.0.3 ALAS2023-2026-1764 May 25, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.