from the OpenSSH 9.9p2 release announcement:
This release fixes two security bugs.
Security
========
* Fix CVE-2025-26465 - ssh(1) in OpenSSH versions 6.8p1 to 9.9p1
(inclusive) contained a logic error that allowed an on-path
attacker (a.k.a MITM) to impersonate any server when the
VerifyHostKeyDNS option is enabled. This option is off by default.
* Fix CVE-2025-26466 - sshd(8) in OpenSSH versions 9.5p1 to 9.9p1
(inclusive) is vulnerable to a memory/CPU denial-of-service related
to the handling of SSH2_MSG_PING packets. This condition may be
mitigated using the existing PerSourcePenalties feature.
Both vulnerabilities were discovered and demonstrated to be exploitable
by the Qualys Security Advisory team. We thank them for their detailed
review of OpenSSH.
💯
See also this blog post discussing this issue and some of the proposed improvements: https://popcar.bearblog.dev/lemmy-needs-to-fix-its-community-separation-problem/
I like their proposed solution #3, but it is somewhat hampered by the DNS-centric model of ActivityPub. I hope that one day something like this proof-of-concept of making AP content-addresable (which i found via this post about "How decentralized is Bluesky really?") will be widely adopted and make instances less important.
But even without such a major change as moving to content addressability, that blog's proposed solution #3 (simply letting communities "follow" other communities) would let readers pick which moderation they like without posters needing to manually cross post to reach everyone: If communities A and B could mutually follow eachother, posts would by default appear on both but could be independently removed from either. 🤔