CVE-2026-22906
Unauthenticated attacker can decrypt credentials stored with AES-ECB using a hardcoded key.
Is CVE-2026-22906 being exploited?
Not confirmed. CVE-2026-22906 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.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-22906?
CVE-2026-22906 is rated Critical with a CVSS score of 9.8. 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-22906?
Yes. A fix has been recorded for CVE-2026-22906. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-22906 affect?
CVE-2026-22906 affects Unknown products/config files storing credentials. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-22906?
Rotate credentials; remove hardcoded keys; migrate to secure vault; avoid AES-ECB.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker can decrypt usernames/passwords from config; potential account takeover, esp. with auth bypass.
Immediate action required
- affected<= 2.64
- affected2.64
- affected<= 2.64
- affected2.64
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.