ALAS2DOCKER-2026-097

References: CVE-2025-61726  CVE-2025-61728  CVE-2025-61730  CVE-2025-61731  CVE-2025-68119  CVE-2025-68121  CVE-2026-22703 
FAQs regarding Amazon Linux ALAS/CVE Severity

Issue Overview:

net/http: memory exhaustion in Request.ParseForm (CVE-2025-61726)

archive/zip: denial of service when parsing arbitrary ZIP archives (CVE-2025-61728)

crypto/tls: handshake messages may be processed at the incorrect encryption level (CVE-2025-61730)

cmd/go: bypass of flag sanitization can lead to arbitrary code execution (CVE-2025-61731)

cmd/go: unexpected code execution when invoking toolchain (CVE-2025-68119)

crypto/tls: Config.Clone copies automatically generated session ticket keys, session resumption does not account for the expiration of full certificate chain (CVE-2025-68121)

Cosign provides code signing and transparency for containers and binaries. Prior to versions 2.6.2 and 3.0.4, Cosign bundle can be crafted to successfully verify an artifact even if the embedded Rekor entry does not reference the artifact's digest, signature or public key. When verifying a Rekor entry, Cosign verifies the Rekor entry signature, and also compares the artifact's digest, the user's public key from either a Fulcio certificate or provided by the user, and the artifact signature to the Rekor entry contents. Without these comparisons, Cosign would accept any response from Rekor as valid. A malicious actor that has compromised a user's identity or signing key could construct a valid Cosign bundle by including any arbitrary Rekor entry, thus preventing the user from being able to audit the signing event. This issue has been patched in versions 2.6.2 and 3.0.4. (CVE-2026-22703)

Issue Correction:
Run yum update runfinch-finch or yum update --advisory ALAS2DOCKER-2026-097 to update your system.

New Packages:

aarch64:
    runfinch-finch-1.14.1-1.amzn2.0.1.aarch64

src:
    runfinch-finch-1.14.1-1.amzn2.0.1.src

x86_64:
    runfinch-finch-1.14.1-1.amzn2.0.1.x86_64