CVE-2026-110688: Cpanel::JSON::XS versions from 4.51 before 4.80 for Perl allow quadratic CPU use by revalidating the remaining buffer per value in incr_parse

Published Oct 19, 2026
·
Updated

Cpanel::JSON::XS versions from 4.51 before 4.80 for Perl allow quadratic CPU use by revalidating the remaining buffer per value in incrparse.

At the first non-ASCII byte in a string, the decoder validates UTF-8 from there to the end of its input. incrparse decodes each buffered value with a fresh decoder, so every value revalidates the rest of the buffer, and doubling the input quadruples the work.

A peer that sends about a megabyte of ordinary non-ASCII JSON in one read ties up the process for seconds of CPU time.

Affected Software

1 affected component
cpan/Cpanel::JSON::XS>=4.51<4.80

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Cpanel::JSON::XS to a version that resolves this vulnerability.

    Fixed in 4.80

Event History

Oct 19, 2026
CVE Published
via MITRE·06:12 PM
Data Sourced
via MITRE·06:12 PM
RemedyDescriptionWeakness
Data Sourced
via NVD·07:17 PM
DescriptionWeakness

Frequently Asked Questions

1

Which deployments are realistically exposed to this issue?

Deployments using Cpanel::JSON::XS from version 4.51 up to, but not including, 4.80 are affected when they use incr_parse on buffered JSON containing non-ASCII string data. The practical exposure is greatest where a peer can supply roughly megabyte-sized JSON input in a single read.

2

What must an attacker do to trigger the CPU consumption?

The attacker needs to cause incremental parsing of multiple buffered values and include ordinary non-ASCII bytes in a JSON string. At the first such byte, UTF-8 validation runs from that point through the remaining input, and each value is parsed with a fresh decoder that repeats the validation.

3

Is a specially malformed JSON payload required?

No. The issue can be triggered with ordinary non-ASCII JSON; the described behavior is caused by repeated UTF-8 validation of the remaining buffer during incremental parsing.

4

What is the impact of increasing the input size?

The processing cost is quadratic: doubling the input can quadruple the work. A peer sending about one megabyte of ordinary non-ASCII JSON in one read can occupy the process for seconds of CPU time.

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