← Search results
CVE-LINKED INVENTORY43 SECURITY RECORDS
GNU
Binutils
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at binutils, 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
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-91782 | 15 Sep 2026 | Binutils: 2.47 | Binutils: 2.48 | Update reference ↗ |
| CVE-2026-91781 | 15 Sep 2026 | Binutils: 2.47 | Binutils: 2.48 | Update reference ↗ |
| CVE-2026-91780 | 15 Sep 2026 | Binutils: 2.47 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-91779 | 15 Sep 2026 | Binutils: 2.47 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-90831 | 14 Sep 2026 | Binutils: 2.47 | 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-90830 | 14 Sep 2026 | Binutils: 2.47 | 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-90829 | 14 Sep 2026 | Binutils: 2.47 | 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-90828 | 14 Sep 2026 | Binutils: 2.47 | 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-90804 | 14 Sep 2026 | Binutils: 2.47 | 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-90803 | 14 Sep 2026 | Binutils: 2.47 | Binutils: 2.48 | Update reference ↗ |
| CVE-2026-90802 | 14 Sep 2026 | Binutils: 2.47 | 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-90801 | 14 Sep 2026 | Binutils: 2.47 | 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-2025-11840 | 16 Oct 2025 | 2.45 | 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-2025-11839 | 16 Oct 2025 | 2.45 | 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-2025-11495 | 8 Oct 2025 | Binutils: 2.45 | 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-2025-11494 | 8 Oct 2025 | Binutils: 2.45 | 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-2025-11414 | 7 Oct 2025 | 2.45 | 2.46 | Update reference ↗ |
| CVE-2025-11413 | 7 Oct 2025 | 2.45 | 2.46 | Update reference ↗ |
| CVE-2025-11412 | 7 Oct 2025 | 2.45 | 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-2025-11083 | 27 Sep 2025 | 2.45 | For OpenShift Container Platform 4.19 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.19/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 values for the release are as follows: (For x86_64 architecture) The image digest is sha256:7bf7c5dabc70518b89130ff7cfe62d14a61ed800adb418359bd9dcaa17b50206 (For s390x architecture) The image digest is sha256:7b2eb7420e10ac8d5e1e5698393235bcad236172c49e688dff2ee651668caf29 (For ppc64le architecture) The image digest is sha256:7213776b521925f53a6a2dfac72adb9a6f9df9710dd39c8847bd6ef211aad63c (For aarch64 architecture) The image digest is sha256:369335090d5f4f5b4853e22c750ef7749ae18320be610d50f7314bb917e2b617 All OpenShift Container Platform 4.19 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.19/html-single/updating_clusters/index#updating-cluster-cli. | Update reference ↗ |
| CVE-2025-11082 | 27 Sep 2025 | 2.45 | 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-2025-11081 | 27 Sep 2025 | Binutils: 2.45 | 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-2025-8225 | 27 Jul 2025 | 2.44 | 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-8224 | 27 Jul 2025 | 2.44 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-7546 | 13 Jul 2025 | 2.45 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-7545 | 13 Jul 2025 | 2.45 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-5245 | 27 May 2025 | 2.0; 2.1; 2.2; 2.3; 2.4; 2.5; 2.6; 2.7 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-5244 | 27 May 2025 | 2.0; 2.1; 2.2; 2.3; 2.4; 2.5; 2.6; 2.7 | 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-2025-3198 | 4 Apr 2025 | 2.43; 2.44 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-1182 | 11 Feb 2025 | 2.43 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-1181 | 11 Feb 2025 | 2.43 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-1180 | 11 Feb 2025 | 2.43 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-1179 | 11 Feb 2025 | 2.43 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-1178 | 11 Feb 2025 | 2.43 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-1176 | 11 Feb 2025 | 2.43 | 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-1153 | 10 Feb 2025 | 2.43; 2.44 | 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-1152 | 10 Feb 2025 | 2.43 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-1151 | 10 Feb 2025 | 2.43 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-1150 | 10 Feb 2025 | 2.43 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-1149 | 10 Feb 2025 | 2.43 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-1148 | 10 Feb 2025 | 2.43 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-1147 | 10 Feb 2025 | 2.43 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-0840 | 29 Jan 2025 | 2.0; 2.1; 2.2; 2.3; 2.4; 2.5; 2.6; 2.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.