External risk intelligence

JSON XS Perl Library Memory Leak Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-124539

This is a vulnerability in a Perl library (JSON::XS) used for processing JSON data. While this library is frequently used in web applications and APIs that may be internet-facing, it is a backend dependency rather than a standalone edge service or appliance. Its exposure depends entirely on how the specific application utilizes the library to process untrusted input, making internet reachability possible but not inherent.

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a memory leak vulnerability in a Perl library used for processing JSON data. If exploited, this could cause applications to consume excessive memory, potentially leading to service disruption. The main concern is to confirm relevance and exposure within our environment.

  • A Perl library can leak memory on bad data.
  • Sustained leaks can crash running applications.
  • Confirm if this Perl library is in use.

Attack Path

How an attacker could exploit the issue

An attacker can trigger a memory exhaustion vulnerability in JSON::XS by repeatedly sending specially crafted JSON data to a running process. This data, when decoded, causes the library to fail to release memory associated with a decoded key. Over time, this repeated failure leads to the depletion of the process's memory, potentially causing it to crash or become unresponsive.

  • Requires network access to the vulnerable process.
  • Triggered by sending invalid JSON input.
  • Risk of denial-of-service due to memory exhaustion.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an attacker to consume excessive memory in a running process by repeatedly sending specially crafted JSON data. When the library encounters a missing colon after a decoded key in a JSON object, it fails to free the decoded key, leading to a memory leak. Over time, this can exhaust the process's available memory.

  • Process memory.
  • Failed JSON decoding.
  • Denial of service.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts Perl applications using JSON::XS, likely managed by application owners and platform teams responsible for the runtime environment. The initial focus should be on inventorying where JSON::XS is deployed, assessing the criticality of affected services, and identifying the accountable personnel before planning remediation.

  • Application owners should own the issue.
  • Verify application use and data reachability.
  • Plan remediation based on identified risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is JSON::XS and how is it used?

JSON::XS is a high-performance Perl library designed for serializing and deserializing JSON data. Developers integrate it into Perl-based applications, web services, and API backends to efficiently process incoming JSON payloads, allowing those programs to convert text into data structures that the software can manipulate.

What is the weakness class for CVE-2026-124539?

This issue is classified as CWE-401: Missing Release of Memory after Effective Lifetime. In the context of CVE-2026-124539, the library fails to properly clean up memory when it encounters a specific malformed JSON input—specifically, a key that lacks a corresponding colon—causing the application to permanently hold onto that memory.

How can an attacker trigger this memory leak?

An attacker triggers the leak by sending deliberately malformed JSON, specifically objects missing the expected colon after a key. Normal, well-formed JSON does not trigger the bug. Because the library fails to free the memory used to decode the key during a failed parsing attempt, repeated submissions effectively drain the process's available memory.

Is my system at risk according to Halo Surface Signal?

Halo Surface Signal notes that while JSON::XS is a backend component rather than a standalone edge device, its reachability depends on your specific application design. If your Perl-based service accepts untrusted JSON input from the network, it may be exposed. You must verify if your application utilizes this library to process external data.

What should I do if my applications use JSON::XS?

Your first step is to inventory your environment to locate all services running versions of JSON::XS prior to 4.05. Once identified, assess how these services handle external input and coordinate with the relevant application owners to plan an update. The primary goal is to upgrade to a patched version that correctly manages memory during decoding failures.

References