CVE-2026-22023
Out-of-bounds heap read in cryptography_aead_encrypt() before v1.4.3 (CWE-125).
Is CVE-2026-22023 being exploited?
Not confirmed. CVE-2026-22023 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.58% probability of exploitation in the next 30 days.
How severe is CVE-2026-22023?
CVE-2026-22023 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-22023?
Yes. A fix has been recorded for CVE-2026-22023. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-22023 affect?
CVE-2026-22023 affects CryptoLib (CCSDS SDLS-EP) prior to 1.4.3. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-22023?
Upgrade to 1.4.3+ immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Potential crash or memory disclosure in the SDLS-EP crypto path; could affect secure space communications.
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.