cve.bz

CVE-2026-41257 jqlang jq: Year 2038 problem, Y2K38, Y2038, Epochalypse

6.4 mediumExploit referenceEPSS 0.1%

Medium (6.4) in jqlang jq. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
jq is a command-line JSON processor. In 1.8.1 and earlier, the jq bytecode VM's data stack tracks its allocation size in a signed int. When the stack grows beyond ≈1 GiB (via deeply nested generator forks), the doubling arithmetic overflows. The wrapped value is passed to realloc and then used for a memmove with attacker-influenced offsets.

Severity

CVSS 4.0

6.4 medium
CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 4th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-05-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
CWE-787 Out-of-bounds Write
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-41257 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-41257?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-41257?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-41257 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.

Badge for a README or a site

CVE-2026-41257

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-41257](https://cve.bz/cve/badge/CVE-2026-41257.svg)](https://cve.bz/cve/CVE-2026-41257)

HTML:

<a href="https://cve.bz/cve/CVE-2026-41257"><img src="https://cve.bz/cve/badge/CVE-2026-41257.svg" alt="CVE-2026-41257"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
jqlang:jqthrough 1.8.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12jq1.6-2.1+deb12u2DEBIAN-CVE-2026-41257
Debian13jq1.7.1-6+deb13u3DEBIAN-CVE-2026-41257
Debian14jq1.8.1-6DEBIAN-CVE-2026-41257
Ubuntu22.04:LTS, 24.04:LTS, 25.10 and 6 morejqno fix listedUBUNTU-CVE-2026-41257
Red Hathummingbird:1jq, jq-devel0:1.8.2-0.1.hum1RHSA-2026:29986
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 11 morejq1.7.1-150000.3.25.1SUSE-SU-2026:4275-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0jq1.7.1-160000.3.1SUSE-SU-2026:22566-1
SUSELinux Micro 6.0jq1.7.1-1.1SUSE-SU-2026:23873-1
SUSELinux Micro 6.1jq1.7.1-slfo.1.1_3.1SUSE-SU-2026:22664-1
SUSELinux Micro 6.2jq1.7.1-160000.3.1SUSE-SU-2026:22545-1
openSUSELeap 16.0jq1.7.1-160000.3.1openSUSE-SU-2026:21248-1
openSUSETumbleweedjq1.8.1-3.1openSUSE-SU-2026:10850-1
Alpinev3.21, v3.22, v3.23 and 1 morejq1.8.2-r0ALPINE-CVE-2026-41257
Azure Linux3jq1.7.1-6AZL-86369
Alpaquita23, streamjq1.8.1-r1BELL-CVE-2026-41257
Alpaquita25jq1.8.1-r2BELL-CVE-2026-41257

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpine · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

To exploit this issue, an attacker needs to supply a crafted JSON input to be processed by jq that triggers deeply nested generator forks. This allows the attacker to overflow the integer used to calculate memory size and cause an out-of-bounds write, effectively resulting in an application crash with no other security impact. Due to these reasons, this vulnerability has been rated with a moderate severity.

Red Hat's mitigation

Do not process untrusted input with the jq command line JSON processor.

ProductPackageStateAdvisory
Red Hat Hardened Imagesjq-main-1.8.2-0.1.hum1Fixed 2026-06-25RHSA-2026:29986
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/controller-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/hub-rhel9Fix deferred
Red Hat Ansible Automation Platform 2automation-controllerFix deferred
Red Hat Ceph Storage 4jqFix deferred
Red Hat Enterprise Linux 10jqFix deferred
Red Hat Enterprise Linux 8jqFix deferred
Red Hat Enterprise Linux 9jqOut of support scope
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Fix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Fix deferred

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-41257.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON