# ALAS2023-2025-1359: amazon-ssm-agent security update

ALAS2023-2025-1359, released January 7, 2026, fixes 15 CVEs in amazon-ssm-agent (version 3.3.3572.0-1.amzn2023). None of them is reported as exploited. Patch Radar priority: High.

- Web page: https://patchblox.com/security/fix/linux/alas2023-2025-1359
- Platform: Linux
- Released: Jan 7, 2026
- Priority: High (Closes CVE-2025-61723, high severity)
- CVEs: 15, exploited: 0, on CISA KEV: 0
- Vendor advisory: https://alas.aws.amazon.com/AL2023/ALAS-2025-1359.html

## Applies to

| Product | Release | Fixed in |
|---|---|---|
| [amazon-ssm-agent](https://patchblox.com/security/data/product/linux/amazon-ssm-agent.md) | amzn 2023 | 3.3.3572.0-1.amzn2023 |

## CVEs this fix closes

| CVE | Priority | Title | CVSS | EPSS | Exploitation |
|---|---|---|---:|---:|---|
| [CVE-2025-61723](https://patchblox.com/security/data/cve/CVE-2025-61723.md) | High | Quadratic complexity when parsing some invalid inputs in encoding/pem | 7.5 | 0.0066 |  |
| [CVE-2025-58185](https://patchblox.com/security/data/cve/CVE-2025-58185.md) | High | Parsing DER payload can cause memory exhaustion in encoding/asn1 | 7.5 | 0.0056 |  |
| [CVE-2025-61724](https://patchblox.com/security/data/cve/CVE-2025-61724.md) | High | Excessive CPU consumption in Reader.ReadResponse in net/textproto | 7.5 | 0.0056 |  |
| [CVE-2025-61729](https://patchblox.com/security/data/cve/CVE-2025-61729.md) | High | Excessive resource consumption when printing error string for host certificate validation in crypto/x509 | 8.1 | 0.0049 |  |
| [CVE-2025-47912](https://patchblox.com/security/data/cve/CVE-2025-47912.md) | High | Insufficient validation of bracketed IPv6 hostnames in net/url | 7.7 | 0.0047 |  |
| [CVE-2025-58189](https://patchblox.com/security/data/cve/CVE-2025-58189.md) | High | ALPN negotiation error contains attacker controlled information in crypto/tls | 7.5 | 0.0047 |  |
| [CVE-2025-58183](https://patchblox.com/security/data/cve/CVE-2025-58183.md) | High | Unbounded allocation when parsing GNU sparse map in archive/tar | 8.2 | 0.0044 |  |
| [CVE-2025-58188](https://patchblox.com/security/data/cve/CVE-2025-58188.md) | High | Panic when validating certificates with DSA public keys in crypto/x509 | 7.5 | 0.0038 |  |
| [CVE-2025-22874](https://patchblox.com/security/data/cve/CVE-2025-22874.md) | High | Usage of ExtKeyUsageAny disables policy validation in crypto/x509 | 7.5 | 0.0038 |  |
| [CVE-2025-4673](https://patchblox.com/security/data/cve/CVE-2025-4673.md) | Routine | Sensitive headers not cleared on cross-origin redirect in net/http | 6.8 | 0.0067 |  |
| [CVE-2025-61725](https://patchblox.com/security/data/cve/CVE-2025-61725.md) | Routine | Excessive CPU consumption in ParseAddress in net/mail | 6.5 | 0.0065 |  |
| [CVE-2025-8556](https://patchblox.com/security/data/cve/CVE-2025-8556.md) | Routine | golang-github-cloudflare-circl: A flaw was found in CIRCL's implementation of the FourQ elliptic curve | 3.7 | 0.0057 |  |
| [CVE-2025-58186](https://patchblox.com/security/data/cve/CVE-2025-58186.md) | Routine | Lack of limit when parsing cookies can cause memory exhaustion in net/http | 5.3 | 0.0057 |  |
| [CVE-2025-58187](https://patchblox.com/security/data/cve/CVE-2025-58187.md) | Routine | Quadratic complexity when checking name constraints in crypto/x509 | 5.3 | 0.0041 |  |
| [CVE-2025-61727](https://patchblox.com/security/data/cve/CVE-2025-61727.md) | Routine | Improper application of excluded DNS name constraints when verifying wildcard names in crypto/x509 | 6.5 | 0.0030 |  |

---

Data as of 2026-11-10T13:56:55Z 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.