cve.bz

CVE-2026-120194 Infinite Loop

7.5 highEPSS 0.5%

High (7.5). EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
A flaw was found in json-glib. The JSONPath slice evaluator used by json_path_query() can enter an infinite loop when given a slice expression with a negative step. An application that evaluates attacker-controlled JSONPath expressions can be forced into a hang, leading to a denial of service.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.5% (unchanged from 0.5% a week ago) estimated probability of exploitation activity in the next 30 days; 42nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-02. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-835 Loop with Unreachable Exit Condition (Infinite Loop)
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-120194 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-120194?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-120194?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-120194 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14json-glibno fix listedDEBIAN-CVE-2026-120194
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morejson-glibno fix listedUBUNTU-CVE-2026-120194
Azure Linux3json-glibno fix listedAZL-112750

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This issue is rated Important. A remote attacker who can supply a crafted JSONPath expression to an application that evaluates it with json-glib's json_path_query() (or equivalent compile-and-match APIs) can trigger a non-terminating loop in the slice evaluator (for example $[:5:-1]), causing a denial of service. Applications that only use fixed, application-defined JSONPath expressions are not exposed. No confidentiality or integrity impact has been demonstrated. No fixed upstream release is available yet; all currently shipped Red Hat and Fedora json-glib builds that include the JSONPath slice evaluator contain the vulnerable loop.

Red Hat's mitigation

Do not evaluate untrusted JSONPath expressions with json_path_query() or json_path_compile()/json_path_match() until a fix is available. Prefer fixed, application-defined path expressions. In particular, reject or avoid slice expressions that specify a negative step.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10json-glibAffected
Red Hat Enterprise Linux 7json-glibAffected
Red Hat Enterprise Linux 8json-glibAffected
Red Hat Enterprise Linux 9json-glibAffected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-120194.

References

Check your stackJSON