| CVE-2025-54236US | —OT critical | 94.7% (100th) | KEV | ✗no fix | 2025-09-09 | ≤ vers:unknown/* |
| CVE-2026-71362US | —OT critical | 90.5% (100th) | KEV | ✓2.4.9-2026-aug, 2.4.8-2026-aug, 2.4.7-2026-aug, 2.4.6-2026-aug | 2026-08-11 | 3 versions |
| CVE-2026-75650US | critical10.0OT critical | 3.95% (90th) | KEV | ✗no fix | 2026-09-07 | ≤ vers:unknown/* |
| CVE-2026-103849US | critical10.0 | 1.17% (67th) | Exploit | ✗no fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2026-48356US | critical9.3 | 1.00% (63rd) | Exploit | ✓2.4.9-2026-jul, 2.4.8-2026-jul, 2.4.7-2026-jul, 2.4.6-2026-jul | 2026-07-14 | 2 versions |
| CVE-2026-34648US | — | 21.4% (98th) | — | ✗no fix | 2026-05-12 | ≤ vers:unknown/* |
| CVE-2026-34650US | — | 15.1% (97th) | — | ✗no fix | 2026-05-12 | ≤ vers:unknown/* |
| CVE-2026-34649US | — | 13.6% (96th) | — | ✗no fix | 2026-05-12 | ≤ vers:unknown/* |
| CVE-2026-48358US | critical9.1 | 1.21% (68th) | — | ✓2.4.9-2026-jul, 2.4.8-2026-jul, 2.4.7-2026-jul, 2.4.6-2026-jul | 2026-07-14 | 2 versions |
| CVE-2026-77110US | high7.6 | 1.09% (65th) | — | ✗no fix | 2026-09-08 | ≤ vers:unknown/* |
| CVE-2026-100133US | critical9.3 | 1.05% (64th) | — | ✗no fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2026-47992US | — | 0.99% (62nd) | — | ✓2.4.9-2026-jul, 2.4.8-2026-jul, 2.4.7-2026-jul, 2.4.6-2026-jul | 2026-07-14 | 2 versions |
| CVE-2026-92922US | high8.1 | 0.90% (59th) | — | ✗no fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2026-91013US | critical9.3 | 0.89% (59th) | — | ✗no fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2026-47996US | medium6.8OT elevated | 0.88% (59th) | — | ✓2.4.9-2026-jul, 2.4.8-2026-jul, 2.4.7-2026-jul, 2.4.6-2026-jul | 2026-07-14 | 2 versions |
| CVE-2026-92464US | critical9.1 | 0.87% (58th) | — | ✗no fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2026-92911US | high8.7 | 0.86% (58th) | — | ✗no fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2026-95631US | high8.7 | 0.86% (58th) | — | ✗no fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2026-77111US | high8.7OT elevated | 0.84% (58th) | — | ✗no fix | 2026-09-08 | ≤ vers:unknown/* |
| CVE-2026-77774US | high8.6OT elevated | 0.83% (57th) | — | ✗no fix | 2026-09-08 | ≤ vers:unknown/* |
| CVE-2026-48416US | —OT elevated | 0.83% (57th) | — | ✓2.4.9-2026-aug, 2.4.8-2026-aug, 2.4.7-2026-aug, 2.4.6-2026-aug | 2026-08-11 | 3 versions |
| CVE-2026-77108US | high7.5OT elevated | 0.82% (57th) | — | ✗no fix | 2026-09-08 | ≤ vers:unknown/* |
| CVE-2026-92909US | critical9.8OT elevated | 0.79% (56th) | — | ✗no fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2026-47988US | high8.6OT elevated | 0.76% (55th) | — | ✓2.4.9-2026-jul, 2.4.8-2026-jul, 2.4.7-2026-jul, 2.4.6-2026-jul | 2026-07-14 | 2 versions |
| CVE-2026-76201US | critical9.3 | 0.74% (54th) | — | ✗no fix | 2026-09-08 | ≤ vers:unknown/* |
| CVE-2026-76200US | critical9.3 | 0.74% (54th) | — | ✗no fix | 2026-09-08 | ≤ vers:unknown/* |
| CVE-2025-47110US | high8.4 | 0.73% (54th) | — | ✗no fix | 2025-06-10 | ≤ vers:adobe/<=2.4.8 |
| CVE-2026-47984US | high8.2OT elevated | 0.73% (54th) | — | ✓2.4.9-2026-jul, 2.4.8-2026-jul, 2.4.7-2026-jul, 2.4.6-2026-jul | 2026-07-14 | 2 versions |
| CVE-2026-47995US | high8.1 | 0.71% (53rd) | — | ✓2.4.9-2026-jul, 2.4.8-2026-jul, 2.4.7-2026-jul, 2.4.6-2026-jul | 2026-07-14 | 2 versions |
| CVE-2026-47998US | —OT elevated | 0.71% (53rd) | — | ✓2.4.9-2026-jul, 2.4.8-2026-jul, 2.4.7-2026-jul, 2.4.6-2026-jul | 2026-07-14 | 2 versions |
| CVE-2026-47997US | —OT elevated | 0.71% (53rd) | — | ✓2.4.9-2026-jul, 2.4.8-2026-jul, 2.4.7-2026-jul, 2.4.6-2026-jul | 2026-07-14 | 2 versions |
| CVE-2026-47994US | high8.7 | 0.70% (53rd) | — | ✓2.4.9-2026-jul, 2.4.8-2026-jul, 2.4.7-2026-jul, 2.4.6-2026-jul | 2026-07-14 | 2 versions |
| CVE-2026-48413US | — | 0.70% (53rd) | — | ✓2.4.9-2026-aug, 2.4.8-2026-aug, 2.4.7-2026-aug, 2.4.6-2026-aug | 2026-08-11 | 3 versions |
| CVE-2026-77109US | high8.6OT elevated | 0.69% (53rd) | — | ✗no fix | 2026-09-08 | ≤ vers:unknown/* |
| CVE-2026-76202US | high8.2OT elevated | 0.67% (52nd) | — | ✗no fix | 2026-09-08 | ≤ vers:unknown/* |
| CVE-2026-34647US | — | 0.65% (51st) | — | ✗no fix | 2026-05-12 | ≤ vers:unknown/* |
| CVE-2026-48411US | medium4.9OT elevated | 0.63% (50th) | — | ✓2.4.9-2026-aug, 2.4.8-2026-aug, 2.4.7-2026-aug, 2.4.6-2026-aug | 2026-08-11 | 3 versions |
| CVE-2025-54264US | — | 0.60% (49th) | — | ✗no fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2026-92908US | high8.3OT elevated | 0.60% (48th) | — | ✗no fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2025-54263US | —OT elevated | 0.60% (48th) | — | ✗no fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2025-43586US | — | 0.57% (47th) | — | ✗no fix | 2025-06-10 | ≤ vers:adobe/<=2.4.8 |
| CVE-2026-34645US | —OT elevated | 0.56% (46th) | — | ✗no fix | 2026-05-12 | ≤ vers:unknown/* |
| CVE-2026-48415US | high8.3OT elevated | 0.56% (46th) | — | ✓2.4.9-2026-aug, 2.4.8-2026-aug, 2.4.7-2026-aug, 2.4.6-2026-aug | 2026-08-11 | 3 versions |
| CVE-2026-48412US | high7.2OT elevated | 0.56% (46th) | — | ✓2.4.9-2026-aug, 2.4.8-2026-aug, 2.4.7-2026-aug, 2.4.6-2026-aug | 2026-08-11 | 3 versions |
| CVE-2025-54265US | medium5.9OT elevated | 0.55% (46th) | — | ✗no fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2025-43585US | — | 0.53% (45th) | — | ✗no fix | 2025-06-10 | ≤ vers:adobe/<=2.4.8 |
| CVE-2025-27207US | — | 0.53% (44th) | — | ✗no fix | 2025-06-10 | ≤ vers:adobe/<=2.4.8 |
| CVE-2026-48001US | — | 0.51% (43rd) | — | ✓2.4.9-2026-jul, 2.4.8-2026-jul, 2.4.7-2026-jul, 2.4.6-2026-jul | 2026-07-14 | 2 versions |
| CVE-2026-95630US | medium4.3 | 0.47% (41st) | — | ✗no fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2025-27206US | — | 0.47% (40th) | — | ✗no fix | 2025-06-10 | ≤ vers:adobe/<=2.4.8 |