CVE-2026-22026
Memory exhaustion DoS in KMC crypto service via unbounded response buffers.
Is CVE-2026-22026 being exploited?
Not confirmed. CVE-2026-22026 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.61% probability of exploitation in the next 30 days.
How severe is CVE-2026-22026?
CVE-2026-22026 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-22026?
Yes. A fix has been recorded for CVE-2026-22026. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-22026 affect?
CVE-2026-22026 affects CryptoLib, KMC crypto service client, core Flight System (cFS), ground station. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-22026?
Upgrade to 1.4.3+ to fix
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Memory growth from oversized HTTP responses leads to DoS; may crash the client/process.
Patch when possible
- affected< 1.4.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.