Invoking auth bypass via unenforced @revoked status in golang.org/x/crypto/ssh/knownhosts
Previously, a revoked 'SignatureKey' belonging to a CA was not correctly checked for revocation.
podman security update
Released 2026-09-14 · Red Hat rating Important · View on Red Hat →
Previously, a revoked 'SignatureKey' belonging to a CA was not correctly checked for revocation.
When adding a key to a remote agent constraint extensions such as [email protected] were not serialized in the request.
The Verify() method for FIDO/U2F security key types ([email protected], [email protected]) did not check the User Presence flag.
A malicious SSH peer could send unsolicited global request responses to fill an internal buffer, blocking the connection's read loop.
An incorrectly placed cast from bytes to int allowed for server-side panic in the AES-GCM packet decoder for well-crafted inputs.
The RSA and DSA public key parsers did not enforce size limits on key parameters.