UBUNTU-CVE-2026-116135: Medium severity ubuntu/libhttp-body-perl vulnerability

Published Nov 3, 2026
·
Updated

HTTP::Body versions before 1.2301 for Perl drop mixed-case percent escapes from urlencoded form fields instead of decoding them. The decode table holds only the all-lowercase and all-uppercase spelling of each hex pair, while the escape pattern matches either case. An escape such as %aB finds no entry and is replaced with nothing, joining the bytes on either side. Hex digits in percent escapes are case-insensitive, and conforming decoders return the byte. A remote attacker can send a field name or value that a conforming decoder in front of the application reads differently, so that pass%aBword reaches the application as password.

Affected Software

7 affected components
ubuntu/libhttp-body-perl*
ubuntu/libhttp-body-perl*
ubuntu/libhttp-body-perl*
ubuntu/libhttp-body-perl*
ubuntu/libhttp-body-perl*
ubuntu/libhttp-body-perl*
ubuntu/libhttp-body-perl*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade HTTP::Body to a version that resolves this vulnerability.

    Fixed in 1.23_01

Event History

Nov 3, 2026
CVE Published
via OSV·12:00 AM
Data Sourced
via OSV·12:00 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Who is realistically exposed to this issue?

Applications using affected HTTP::Body versions to parse application/x-www-form-urlencoded request fields are exposed when another component, such as a proxy or gateway, decodes those fields according to standard case-insensitive percent-escape handling. The risk is a parsing discrepancy between that component and the application.

2

What does an attacker need to exploit it?

An attacker needs to be able to submit URL-encoded form field names or values containing mixed-case percent escapes, such as %aB. The attacker can use this to cause HTTP::Body to remove the escaped byte while a conforming decoder interprets it as the corresponding byte.

3

How can I tell whether an application is affected?

Check whether it uses HTTP::Body before version 1.23_01 and parses URL-encoded form data. Test a field containing a mixed-case escape, such as pass%aBword; an affected parser produces password rather than decoding %aB as a byte.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203