Bug 2458084 (CVE-2026-40164)
| Summary: | CVE-2026-40164 jq: jq: Denial of Service via crafted JSON object causing hash collisions | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | OSIDB Bzimport <bzimport> |
| Component: | vulnerability | Assignee: | Product Security <prodsec-ir-bot> |
| Status: | NEW --- | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | CC: | akhatavk, amctagga, aoconnor, aos-team-art-private, asdas, bniver, dpaolell, flucifre, gmeno, groman, jdelft, jupierce, lgarciaa, mbenjamin, mbiarnes, mhackett, ppalepu, ppostler, prdhamdh, rhel-process-autobot, sghai, sidsharm, sostapov, suppawar, vereddy, vlaad, watson-tool-maintainers |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: |
A flaw was found in jq, a command-line JSON processor. A remote attacker could exploit this vulnerability by providing a specially crafted JSON object. This object leverages a weakness in jq's hashing algorithm, which uses a hardcoded, publicly known seed. By crafting the JSON object to cause hash collisions, an attacker can degrade the performance of JSON object hash table operations, leading to significant CPU exhaustion and a denial of service (DoS) for systems processing the malicious JSON data.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2458368 | ||
| Bug Blocks: | |||
|
Description
OSIDB Bzimport
2026-04-14 00:01:27 UTC
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2026:16252 https://access.redhat.com/errata/RHSA-2026:16252 This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:16693 https://access.redhat.com/errata/RHSA-2026:16693 This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:16692 https://access.redhat.com/errata/RHSA-2026:16692 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions Via RHSA-2026:18045 https://access.redhat.com/errata/RHSA-2026:18045 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions Via RHSA-2026:18044 https://access.redhat.com/errata/RHSA-2026:18044 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.6 Extended Update Support Via RHSA-2026:18042 https://access.redhat.com/errata/RHSA-2026:18042 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions Red Hat Enterprise Linux 8.8 Telecommunications Update Service Via RHSA-2026:18046 https://access.redhat.com/errata/RHSA-2026:18046 This issue has been addressed in the following products: Red Hat Enterprise Linux 10.0 Extended Update Support Via RHSA-2026:18040 https://access.redhat.com/errata/RHSA-2026:18040 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On Via RHSA-2026:18048 https://access.redhat.com/errata/RHSA-2026:18048 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions Red Hat Enterprise Linux 8.6 Telecommunications Update Service Via RHSA-2026:18047 https://access.redhat.com/errata/RHSA-2026:18047 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.4 Extended Update Support Via RHSA-2026:18043 https://access.redhat.com/errata/RHSA-2026:18043 This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:19151 https://access.redhat.com/errata/RHSA-2026:19151 This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:19365 https://access.redhat.com/errata/RHSA-2026:19365 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.19 Via RHSA-2026:23245 https://access.redhat.com/errata/RHSA-2026:23245 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.15 Via RHSA-2026:23233 https://access.redhat.com/errata/RHSA-2026:23233 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.18 Via RHSA-2026:25181 https://access.redhat.com/errata/RHSA-2026:25181 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.16 Via RHSA-2026:25044 https://access.redhat.com/errata/RHSA-2026:25044 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.12 Via RHSA-2026:26528 https://access.redhat.com/errata/RHSA-2026:26528 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.13 Via RHSA-2026:26542 https://access.redhat.com/errata/RHSA-2026:26542 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.14 Via RHSA-2026:28887 https://access.redhat.com/errata/RHSA-2026:28887 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.17 Via RHSA-2026:34098 https://access.redhat.com/errata/RHSA-2026:34098 |