Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY23 SECURITY RECORDS

jqlang

jq

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

Official registry publication history is available at jq, but registry activity is not a publisher support boundary.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-47770 25 Jun 2026 < 1.8.2 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Update reference ↗
CVE-2026-49839 25 Jun 2026 < 1.8.2 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Update reference ↗
CVE-2026-54679 25 Jun 2026 < 1.8.2 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Update reference ↗
CVE-2026-43896 11 May 2026 <= 1.8.1 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Update reference ↗
CVE-2026-43895 11 May 2026 <= 1.8.1 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Update reference ↗
CVE-2026-44777 11 May 2026 <= 1.8.2rc1 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Update reference ↗
CVE-2026-43894 11 May 2026 <= 1.8.1 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Update reference ↗
CVE-2026-41256 11 May 2026 <= 1.8.1 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Update reference ↗
CVE-2026-40612 11 May 2026 <= 1.8.1 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Update reference ↗
CVE-2026-41257 11 May 2026 <= 1.8.1 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Update reference ↗
CVE-2026-33948 13 Apr 2026 < 6374ae0bcdfe33a18eb0ae6db28493b1f34a0a5b For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Update reference ↗
CVE-2026-40164 13 Apr 2026 jq: < 0c7d133c3c7e37c00b6d46b658a02244fdd3c784 RHSA-2026:26528: Red Hat OpenShift Container Platform 4.12 Update reference ↗
CVE-2026-39979 13 Apr 2026 < 2f09060afab23fe9390cce7cb860b10416e1bf5f For OpenShift Container Platform 4.12 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.12/html/release_notes You may download the oc tool and use it to inspect release image metadata for x86_64 architecture. The image digest may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha value for the release is as follows: (For x86_64 architecture) The image digest is sha256:4d3bbcec187be94449a001896fcd21e41580dbba1cac38717905a2cb31a94a6e All OpenShift Container Platform 4.12 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at https://docs.redhat.com/en/documentation/openshift_container_platform/4.12/html-single/updating_clusters/index#updating-cluster-within-minor. Update reference ↗
CVE-2026-39956 13 Apr 2026 jq: < 1.8.2 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2026-33947 13 Apr 2026 < fb59f1491058d58bdc3e8dd28f1773d1ac690a1f An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2026-32316 13 Apr 2026 < e47e56d226519635768e6aab2f38f0ab037c09e5 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2025-9403 25 Aug 2025 1.0; 1.1; 1.2; 1.3; 1.4; 1.5; 1.6 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2025-49014 19 Jun 2025 = 1.8.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-48060 21 May 2025 <= 1.7.1 For OpenShift Container Platform 4.13 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.13/html/release_notes You may download the oc tool and use it to inspect release image metadata for x86_64, s390x, ppc64le, and aarch64 architectures. The image digests may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha value for the release is as follows: (For x86_64 architecture) The image digest is sha256:32f55a5ff24713e240a293ced4f8cb202bbdf482095593e226d1ea4397fefe8e All OpenShift Container Platform 4.13 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at https://docs.redhat.com/en/documentation/openshift_container_platform/4.13/html-single/updating_clusters/index#updating-cluster-within-minor. Update reference ↗
CVE-2024-23337 21 May 2025 <= 1.7.1 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2024-53427 26 Feb 2025 ≤ 1.7.1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-50268 13 Dec 2023 = 1.7 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2023-50246 13 Dec 2023 = 1.7 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.