ibm verify identity access container
ProduktUScpe:2.3:a:ibm:verify_identity_access_container:*:*:*:*:*:*:*:*
Ein im Bedrohungsgraphen erfasstes Produkt; die Schwachstellen unten betreffen es bekanntermaßen.
nach Schweregrad
4critical15high13medium0low
aktualisiert 2026-10-24
| ID | Schweregrad CVSS-Basis-Schweregrad und -Wert (0–10). | EPSS FIRST.org-Wahrscheinlichkeit einer Ausnutzung in den nächsten 30 Tagen, mit Perzentil-Rang unter allen CVEs. | ausnutzbar Auf CISAs Liste bekannter ausgenutzter Schwachstellen (KEV) oder ein öffentlicher Exploit liegt vor. | behoben Ob für einen betroffenen Bereich eine behobene Version vorliegt. | veröffentlicht | betroffen |
|---|
| CVE-2026-78401US | critical9.8 | 0.57% (46th) | — | ✗kein Fix | 2026-10-08 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-12618US | — | 0.54% (45th) | — | ✗kein Fix | 2026-08-12 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-12005US | — | 0.54% (45th) | — | ✗kein Fix | 2026-08-12 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-4101US | critical9.8 | 0.52% (43rd) | — | ✗kein Fix | 2026-04-01 | 11.0.0.0 → 11.0.2.0 |
| CVE-2026-78406US | critical9.8 | 0.50% (42nd) | — | ✗kein Fix | 2026-10-08 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-12004US | — | 0.49% (42nd) | — | ✗kein Fix | 2026-08-12 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-11932US | high7.5 | 0.46% (39th) | — | ✗kein Fix | 2026-08-12 | 11.0.0.0 → 11.0.3 |
| CVE-2026-12359US | — | 0.45% (38th) | — | ✗kein Fix | 2026-08-12 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-16916US | high8.8 | 0.42% (35th) | — | ✗kein Fix | 2026-10-08 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-19482US | high8.8 | 0.42% (35th) | — | ✗kein Fix | 2026-10-08 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-11904US | medium5.3 | 0.40% (33rd) | — | ✗kein Fix | 2026-07-30 | 2 Versionen |
| CVE-2026-8861US | medium5.3 | 0.40% (33rd) | — | ✗kein Fix | 2026-07-17 | 11.0.0.0 → 11.0.2 |
| CVE-2026-2862US | — | 0.40% (33rd) | — | ✗kein Fix | 2026-04-01 | 11.0.0.0 → 11.0.2.0 |
| CVE-2026-17616US | critical9.8 | 0.40% (33rd) | — | ✗kein Fix | 2026-08-12 | 11.0.0.0 → 11.0.3 |
| CVE-2026-1491US | — | 0.37% (30th) | — | ✗kein Fix | 2026-04-01 | 11.0.0.0 → 11.0.2.0 |
| CVE-2026-19493US | high7.5 | 0.36% (29th) | — | ✗kein Fix | 2026-10-08 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-7364US | medium6.1 | 0.36% (28th) | — | ✗kein Fix | 2026-07-17 | 11.0.0.0 → 11.0.2.0 |
| CVE-2026-1345US | — | 0.36% (28th) | — | ✗kein Fix | 2026-04-01 | 11.0.0.0 → 11.0.2.0 |
| CVE-2026-18740US | high8.8 | 0.35% (28th) | — | ✗kein Fix | 2026-10-08 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-13267US | — | 0.35% (27th) | — | ✗kein Fix | 2026-08-12 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-19491US | high7.5 | 0.33% (25th) | — | ✗kein Fix | 2026-10-08 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-16823US | high7.5 | 0.33% (25th) | — | ✗kein Fix | 2026-10-08 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-11923US | — | 0.32% (24th) | — | ✗kein Fix | 2026-08-12 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-4938US | —OT erhöht | 0.30% (22nd) | — | ✗kein Fix | 2026-07-17 | 11.0.0.0 → 11.0.2.0 |
| CVE-2026-12091US | medium5.3 | 0.30% (21st) | — | ✗kein Fix | 2026-10-08 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-11937US | — | 0.29% (21st) | — | ✗kein Fix | 2026-08-12 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-19494US | medium6.5 | 0.29% (20th) | — | ✗kein Fix | 2026-10-08 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-19498US | high7.5 | 0.28% (19th) | — | ✗kein Fix | 2026-10-08 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-78399US | medium6.5 | 0.27% (18th) | — | ✗kein Fix | 2026-10-08 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-2475US | medium4.7 | 0.25% (16th) | — | ✗kein Fix | 2026-04-01 | 11.0.0.0 → 11.0.2.0 |
| CVE-2026-5926US | —OT erhöht | 0.23% (13th) | — | ✗kein Fix | 2026-04-23 | 11.0.0.0 → 11.0.2.0 |
| CVE-2026-19878US | medium6.5 | 0.23% (13th) | — | ✗kein Fix | 2026-10-08 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-1346US | high7.8 | 0.23% (13th) | — | ✗kein Fix | 2026-04-08 | 11.0.0.0 → 11.0.2.0 |
| CVE-2026-12109US | high7.2 | 0.21% (11th) | — | ✗kein Fix | 2026-10-08 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-16830US | medium5.4 | 0.21% (10th) | — | ✗kein Fix | 2026-10-08 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-1343US | high7.2 | 0.20% (9th) | — | ✗kein Fix | 2026-04-08 | 11.0.0.0 → 11.0.2.0 |
| CVE-2026-11930US | high7.5 | 0.19% (9th) | — | ✗kein Fix | 2026-10-08 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-11939US | medium5.3 | 0.18% (7th) | — | ✗kein Fix | 2026-10-08 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-1342US | high7.9 | 0.18% (7th) | — | ✗kein Fix | 2026-04-08 | 11.0.0.0 → 11.0.2.0 |
| CVE-2026-11888US | high7.5 | 0.17% (6th) | — | ✗kein Fix | 2026-10-08 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-4364US | — | 0.15% (4th) | — | ✗kein Fix | 2026-04-01 | 11.0.0.0 → 11.0.2.0 |
| CVE-2026-17189US | medium6.1 | 0.15% (4th) | — | ✗kein Fix | 2026-10-08 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-78407US | medium5.4 | 0.14% (3rd) | — | ✗kein Fix | 2026-10-08 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-11936US | medium5.4 | 0.12% (2nd) | — | ✗kein Fix | 2026-10-08 | 11.0.0.0 → 11.0.3.0 |
| CVE-2026-78388US | high8.8 | 0.11% (1st) | — | ✗kein Fix | 2026-10-08 | 11.0.0.0 → 11.0.3.0 |