CVE-2025-22869 is an uncontrolled memory-consumption vulnerability in the SSH server implementation of golang.org/x/crypto/ssh. An affected SSH server that implements a file-transfer protocol can read pending content into memory while an SSH client delays completion of key exchange or never completes it. Because the content cannot be transmitted until key exchange completes, the server retains the buffered data, enabling memory exhaustion.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
50 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability in a dependency addressed by upgrading golang.org/x/crypto to v0.35.0 as part of the git-lfs package update.
A vulnerability referenced by the openSUSE-SU-2026:21603-1 advisory as affecting installed gitea-tea-related packages; no further technical detail is provided in the content.
A vulnerability included in the RHSA-2025:3301 CVE list; the advisory provides no technical description.
A denial-of-service vulnerability in golang.org/x/crypto/ssh key exchange processing.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.