Bug 2458077 (CVE-2026-39979)
| Summary: | CVE-2026-39979 jq: out-of-bounds read in jv_parse_sized() on error formatting for non-NUL-terminated buffers | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | OSIDB Bzimport <bzimport> |
| Component: | vulnerability | Assignee: | Product Security DevOps Team <prodsec-dev> |
| Status: | NEW --- | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | CC: | adudiak, amctagga, aoconnor, bniver, crizzo, dschmidt, erezende, flucifre, gmeno, groman, jlanda, jmitchel, kshier, mbenjamin, mhackett, pbohmill, rhel-process-autobot, simaishi, smcdonal, sostapov, stcannon, teagle, vereddy, watson-tool-maintainers, yguenane |
| 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, specifically in the libjq API. Parsing a malformed JSON input from a non-NUL-terminated buffer using the `jv_parse_sized` function can cause an out-of-bounds read, resulting in an application crash and a possible memory disclosure within the error message generated by the parser.
|
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: | 2458400 | ||
| Bug Blocks: | |||
|
Description
OSIDB Bzimport
2026-04-13 23:01:25 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 |