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

golang.org/x/crypto

golang.org/x/crypto/ssh/agent

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

Lifecycle evidence status

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

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-46598 22 May 2026 < 0.52.0 Before applying this update, make sure all previously released errata relevant to your system have been applied. Update reference ↗
CVE-2026-39832 22 May 2026 golang.org/x/crypto/ssh/agent: < 0.52.0 RHSA-2026:41019: RHEM 1.1 for RHEL 10, RHEM 1.1 for RHEL 9 Update reference ↗
CVE-2026-39833 22 May 2026 < 0.52.0 Before applying this update, make sure all previously released errata relevant to your system have been applied. Update reference ↗
CVE-2025-47914 19 Nov 2025 < 0.45.0 Before applying this update, make sure all previously released errata relevant to your system have been applied. Update reference ↗
CVE-2025-47913 13 Nov 2025 < 0.43.0 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/11258 For supported configurations, refer to: https://access.redhat.com/articles/1548993 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.