Go standard library
crypto/x509
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
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-27145 | 2 Jun 2026 | crypto/x509: < 1.25.11, 1.26.0-0 < 1.26.4 | RHSA-2026:42079: Red Hat Ansible Automation Platform 2.6 for RHEL 10, Red Hat Ansible Automation Platform 2.6 for RHEL 9 | Update reference ↗ |
| CVE-2026-32280 | 8 Apr 2026 | crypto/x509: < 1.25.9, 1.26.0-0 < 1.26.2 | RHSA-2026:24762: Red Hat Ansible Automation Platform 2.6 for RHEL 10, Red Hat Ansible Automation Platform 2.6 for RHEL 9 | Update reference ↗ |
| CVE-2026-32281 | 8 Apr 2026 | < 1.25.9; 1.26.0-0 < 1.26.2 | For details on how to apply this update, refer to Ansible Automation Platform documentation. | Update reference ↗ |
| CVE-2026-33810 | 8 Apr 2026 | crypto/x509: 1.26.0-0 < 1.26.2 | RHSA-2026:68334: RHEM 1.1 for RHEL 10, RHEM 1.1 for RHEL 9 | Update reference ↗ |
| CVE-2026-27138 | 6 Mar 2026 | 1.26.0-0 < 1.26.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-27137 | 6 Mar 2026 | crypto/x509: 1.26.0-0 < 1.26.1 | RHSA-2026:41019: RHEM 1.1 for RHEL 10, RHEM 1.1 for RHEL 9 | Update reference ↗ |
| CVE-2025-61727 | 3 Dec 2025 | < 1.24.11; 1.25.0 < 1.25.5 | 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-61729 | 2 Dec 2025 | < 1.24.11; 1.25.0 < 1.25.5 | For details on how to apply this update, refer to Ansible Automation Platform documentation. | Update reference ↗ |
| CVE-2025-58188 | 29 Oct 2025 | crypto/x509: < 1.24.8, 1.25.0 < 1.25.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-2025-58187 | 29 Oct 2025 | crypto/x509: < 1.24.9, 1.25.0 < 1.25.3 | 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-22874 | 11 Jun 2025 | 1.24.0-0 < 1.24.4 | 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-22865 | 28 Jan 2025 | 1.24.0-0 < 1.24.0-rc.2 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/2789521 For supported configurations, refer to: https://access.redhat.com/articles/1548993 | Update reference ↗ |
| CVE-2024-45341 | 28 Jan 2025 | < 1.22.11; 1.23.0-0 < 1.23.5; 1.24.0-0 < 1.24.0-rc.2 | 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-24783 | 5 Mar 2024 | < 1.21.8; 1.22.0-0 < 1.22.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
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.