Quick answers
- Is CVE-2026-110673 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110673 being exploited in the wild.
- How severe is CVE-2026-110673?
- Informational severity, published 19 October 2026.
- Which products and versions are affected?
- cPanel JSON::XS before 4.80.
- Is there a fix for CVE-2026-110673?
- Yes: fixed in Cpanel::JSON::XS 4.80. Until then: Disable the allow_tags feature if not required, or restrict parsing to trusted JSON sources until upgraded to version 4.80 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-110673 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-110673?
- Check whether you run cPanel JSON::XS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Cpanel::JSON::XS 4.80
Disable the allow_tags feature if not required, or restrict parsing to trusted JSON sources until upgraded to version 4.80 or later.
Technical details
The vulnerability is a stack exhaustion flaw in the decode_tag function when allow_tags is enabled. Tagged values (marked by "(" syntax) are decoded recursively but were not counted against the max_depth limit, unlike arrays and objects. An attacker can send deeply nested tagged values (e.g., many "(" bytes in sequence) to exhaust the C stack and trigger an uncatchable segmentation fault. The fix charges tagged value decoding against max_depth to enforce the depth limit.
Affected products
- Cpanel JSON::XS before 4.80
Timeline
- 2026-10-19: disclosed