# golang-go.crypto security updates Patch Radar has 32 security fixes for golang-go.crypto, closing 25 CVEs. The newest security fix is DEBIAN-CVE-2026-56855 (1:0.56.0-1), released September 8, 2026. - Web page: https://patchblox.com/security/product/linux/golang-go.crypto - Platform: Linux - Supported: yes ## Security fixes, newest first | Fix | Released | Fixed in | Priority | CVEs | Exploited | |---|---|---|---|---:|---:| | [DEBIAN-CVE-2026-56855](https://patchblox.com/security/data/fix/linux/debian-cve-2026-56855.md) | Sep 8, 2026 | Debian 14 1:0.56.0-1 | High | 1 | 0 | | [DEBIAN-CVE-2026-78662](https://patchblox.com/security/data/fix/linux/debian-cve-2026-78662.md) | Sep 8, 2026 | Debian 14 1:0.56.0-1 | High | 1 | 0 | | [DEBIAN-CVE-2026-56854](https://patchblox.com/security/data/fix/linux/debian-cve-2026-56854.md) | Aug 29, 2026 | Debian 14 1:0.55.0-1 | High | 1 | 0 | | [DEBIAN-CVE-2026-46597](https://patchblox.com/security/data/fix/linux/debian-cve-2026-46597.md) | May 22, 2026 | Debian 14 1:0.52.0-1 | High | 1 | 0 | | [DEBIAN-CVE-2026-46598](https://patchblox.com/security/data/fix/linux/debian-cve-2026-46598.md) | May 22, 2026 | Debian 14 1:0.52.0-1 | Routine | 1 | 0 | | [DEBIAN-CVE-2026-46595](https://patchblox.com/security/data/fix/linux/debian-cve-2026-46595.md) | May 22, 2026 | Debian 14 1:0.52.0-1 | Urgent | 1 | 0 | | [DEBIAN-CVE-2026-42508](https://patchblox.com/security/data/fix/linux/debian-cve-2026-42508.md) | May 22, 2026 | Debian 14 1:0.52.0-1 | High | 1 | 0 | | [DEBIAN-CVE-2026-39834](https://patchblox.com/security/data/fix/linux/debian-cve-2026-39834.md) | May 22, 2026 | Debian 14 1:0.52.0-1 | High | 1 | 0 | | [DEBIAN-CVE-2026-39835](https://patchblox.com/security/data/fix/linux/debian-cve-2026-39835.md) | May 22, 2026 | Debian 14 1:0.52.0-1 | High | 1 | 0 | | [DEBIAN-CVE-2026-39832](https://patchblox.com/security/data/fix/linux/debian-cve-2026-39832.md) | May 22, 2026 | Debian 14 1:0.52.0-1 | High | 1 | 0 | | [DEBIAN-CVE-2026-39830](https://patchblox.com/security/data/fix/linux/debian-cve-2026-39830.md) | May 22, 2026 | Debian 14 1:0.52.0-1 | High | 1 | 0 | | [DEBIAN-CVE-2026-39831](https://patchblox.com/security/data/fix/linux/debian-cve-2026-39831.md) | May 22, 2026 | Debian 14 1:0.52.0-1 | High | 1 | 0 | | [DEBIAN-CVE-2026-39833](https://patchblox.com/security/data/fix/linux/debian-cve-2026-39833.md) | May 22, 2026 | Debian 14 1:0.52.0-1 | High | 1 | 0 | | [DEBIAN-CVE-2026-39829](https://patchblox.com/security/data/fix/linux/debian-cve-2026-39829.md) | May 22, 2026 | Debian 14 1:0.52.0-1 | High | 1 | 0 | | [DEBIAN-CVE-2026-39828](https://patchblox.com/security/data/fix/linux/debian-cve-2026-39828.md) | May 22, 2026 | Debian 14 1:0.52.0-1 | High | 1 | 0 | | [DEBIAN-CVE-2026-39827](https://patchblox.com/security/data/fix/linux/debian-cve-2026-39827.md) | May 22, 2026 | Debian 14 1:0.52.0-1 | Routine | 1 | 0 | | [DEBIAN-CVE-2025-58181](https://patchblox.com/security/data/fix/linux/debian-cve-2025-58181.md) | Nov 19, 2025 | Debian 14 1:0.45.0-1 | Routine | 1 | 0 | | [DEBIAN-CVE-2025-47914](https://patchblox.com/security/data/fix/linux/debian-cve-2025-47914.md) | Nov 19, 2025 | Debian 14 1:0.45.0-1 | Routine | 1 | 0 | | [DEBIAN-CVE-2025-47913](https://patchblox.com/security/data/fix/linux/debian-cve-2025-47913.md) | Nov 13, 2025 | Debian 14 1:0.43.0-1 | High | 1 | 0 | | [DEBIAN-CVE-2025-22869](https://patchblox.com/security/data/fix/linux/debian-cve-2025-22869.md) | Feb 26, 2025 | Debian 14 1:0.42.0-1 | High | 1 | 0 | | [DEBIAN-CVE-2024-45337](https://patchblox.com/security/data/fix/linux/debian-cve-2024-45337.md) | Dec 12, 2024 | Debian 14 1:0.42.0-1 | High | 1 | 0 | | [DEBIAN-CVE-2022-30636](https://patchblox.com/security/data/fix/linux/debian-cve-2022-30636.md) | Jul 2, 2024 | Debian 12.15 (bookworm) 1:0.0~git20220829.c86fa9a-1 | High | 1 | 0 | | [DEBIAN-CVE-2022-30636](https://patchblox.com/security/data/fix/linux/debian-cve-2022-30636.md) | Jul 2, 2024 | Debian 13.5 (trixie) 1:0.0~git20220829.c86fa9a-1 | High | 1 | 0 | | [DEBIAN-CVE-2022-30636](https://patchblox.com/security/data/fix/linux/debian-cve-2022-30636.md) | Jul 2, 2024 | Debian 14 1:0.0~git20220829.c86fa9a-1 | High | 1 | 0 | | [DEBIAN-CVE-2023-48795](https://patchblox.com/security/data/fix/linux/debian-cve-2023-48795.md) | Dec 18, 2023 | Debian 13.5 (trixie) 1:0.17.0-1 | High | 1 | 0 | | [DEBIAN-CVE-2023-48795](https://patchblox.com/security/data/fix/linux/debian-cve-2023-48795.md) | Dec 18, 2023 | Debian 14 1:0.17.0-1 | High | 1 | 0 | | [DEBIAN-CVE-2021-43565](https://patchblox.com/security/data/fix/linux/debian-cve-2021-43565.md) | Sep 6, 2022 | Debian 12.15 (bookworm) 1:0.0~git20211202.5770296-1 | High | 1 | 0 | | [DEBIAN-CVE-2021-43565](https://patchblox.com/security/data/fix/linux/debian-cve-2021-43565.md) | Sep 6, 2022 | Debian 13.5 (trixie) 1:0.0~git20211202.5770296-1 | High | 1 | 0 | | [DEBIAN-CVE-2021-43565](https://patchblox.com/security/data/fix/linux/debian-cve-2021-43565.md) | Sep 6, 2022 | Debian 14 1:0.0~git20211202.5770296-1 | High | 1 | 0 | | [DEBIAN-CVE-2022-27191](https://patchblox.com/security/data/fix/linux/debian-cve-2022-27191.md) | Mar 18, 2022 | Debian 12.15 (bookworm) 1:0.0~git20220315.3147a52-1 | High | 1 | 0 | | [DEBIAN-CVE-2022-27191](https://patchblox.com/security/data/fix/linux/debian-cve-2022-27191.md) | Mar 18, 2022 | Debian 13.5 (trixie) 1:0.0~git20220315.3147a52-1 | High | 1 | 0 | | [DEBIAN-CVE-2022-27191](https://patchblox.com/security/data/fix/linux/debian-cve-2022-27191.md) | Mar 18, 2022 | Debian 14 1:0.0~git20220315.3147a52-1 | High | 1 | 0 | --- Data as of 2026-11-10T07:50:38Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.