How severe is CVE-2026-22906?

CVE-2026-22906 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-22906 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (26th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-22906?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

Does CVE-2026-22906 have an EU (EUVD) identifier?

Yes. CVE-2026-22906 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-6926.

When was CVE-2026-22906 published?

CVE-2026-22906 was published on 2026-02-09 and last updated on 2026-06-17.

CVE-2026-22906

CVE-2026-22906 is a critical-severity vulnerability with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-321.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
EPSS exploit prediction: 0% (26th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-6926
Weakness: CWE-321
Published: 2026-02-09
Last modified: 2026-06-17

Description

User credentials are stored using AES‑ECB encryption with a hardcoded key. An unauthenticated remote attacker obtaining the configuration file can decrypt and recover plaintext usernames and passwords, especially when combined with the authentication bypass.

Frequently asked questions

What is CVE-2026-22906?: User credentials are stored using AES‑ECB encryption with a hardcoded key. An unauthenticated remote attacker obtaining the configuration file can decrypt and recover plaintext usernames and passwords, especially when combined with the authentication bypass.
How severe is CVE-2026-22906?: CVE-2026-22906 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-22906 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (26th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-22906?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2026-22906 have an EU (EUVD) identifier?: Yes. CVE-2026-22906 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-6926.
When was CVE-2026-22906 published?: CVE-2026-22906 was published on 2026-02-09 and last updated on 2026-06-17.

References

https://certvde.com/de/advisories/VDE-2026-004

Other CWE-321 vulnerabilities

CVE-2024-30207 — Critical (CVSS 10.0): A vulnerability has been identified in SIMATIC RTLS Locating Manager (6GT2780-0DA00) (All versions < V3.0.1.1), SIMATIC…
CVE-2014-5419 — Critical (CVSS 10.0): GE Multilink ML800, ML1200, ML1600, and ML2400 switches with firmware 4.2.1 and earlier and Multilink ML810, ML3000,…
CVE-2024-35344 — Critical (CVSS 9.9): Certain Anpviz products contain a hardcoded cryptographic key stored in the firmware of the device. This affects…
CVE-2026-16504 — Critical (CVSS 9.8): Deployment of the VPS.org one-click Zulip template deploys a hardcoded application signing key, a default database…
CVE-2021-32086 — Critical (CVSS 9.8): An issue was discovered in Quest KACE Systems Deployment Appliance (SMA) 11.0.273. It uses a hardcoded symmetric…
CVE-2026-47410 — Critical (CVSS 9.8): PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Versions prior to 0.1.4 have an…

Browse all CWE-321 vulnerabilities →