OpenClaw vulnerabilities, one by one
This tracker lists every vulnerability the NVD publishes for OpenClaw, with its severity and, when the description gives it, the version that fixes it. Most are fixed in later releases: the practical rule is to run a recent version, which is what we maintain.
Filter the list
685 vulnerabilities: 31 critical, 287 high, 337 medium, 30 low. Latest published on October 14, 2026. Data fetched from the NVD on October 23, 2026.
| CVE | Published | CVSS | Severity | Type | Fixed in |
|---|---|---|---|---|---|
| CVE-2026-110689 | 10/14/2026 | 5.3 | Medium | Other | Not stated |
| CVE-2026-108757 | 10/11/2026 | 6.5 | Medium | Authentication flaw | Not stated |
| CVE-2026-108156 | 10/09/2026 | 7.1 | High | Path traversal | Not stated |
| CVE-2026-101880 | 09/30/2026 | 8.8 | High | Authorisation flaw | 2026.7.1 |
| CVE-2026-101882 | 09/30/2026 | 8.8 | High | Command execution or injection | 2026.7.1 |
| CVE-2026-101884 | 09/30/2026 | 7.5 | High | Command execution or injection | 2026.7.1 |
| CVE-2026-101879 | 09/30/2026 | 6.5 | Medium | Authorisation flaw | 2026.7.1-3 |
| CVE-2026-101881 | 09/30/2026 | 6.5 | Medium | Resource exhaustion | 2026.7.1 |
| CVE-2026-101883 | 09/30/2026 | 5.4 | Medium | Server-side request forgery | Not stated |
| CVE-2026-102806 | 09/29/2026 | 6.3 | Medium | Authorisation flaw | 2026.9.5 |
| CVE-2026-102807 | 09/29/2026 | 5.3 | Medium | Authorisation flaw | 2026.9.4 |
| CVE-2026-100544 | 09/26/2026 | 8.8 | High | Authorisation flaw | 2026.8.1 |
| CVE-2026-100552 | 09/26/2026 | 8.8 | High | Authorisation flaw | 2026.8.1 |
| CVE-2026-100575 | 09/26/2026 | 8.8 | High | Authorisation flaw | 2026.8.1 |
| CVE-2026-100580 | 09/26/2026 | 8.8 | High | Other | 2026.7.1 |
| CVE-2026-100586 | 09/26/2026 | 8.8 | High | Authorisation flaw | 2026.7.1 |
| CVE-2026-100587 | 09/26/2026 | 8.8 | High | Authorisation flaw | 2026.7.1 |
| CVE-2026-100596 | 09/26/2026 | 8.8 | High | Authorisation flaw | 2026.7.1 |
| CVE-2026-100599 | 09/26/2026 | 8.8 | High | Command execution or injection | Not stated |
| CVE-2026-100551 | 09/26/2026 | 8.3 | High | Other | Not stated |
| CVE-2026-100557 | 09/26/2026 | 8.3 | High | Authorisation flaw | 2026.8.1 |
| CVE-2026-100568 | 09/26/2026 | 8.3 | High | Information exposure | 2026.8.1 |
| CVE-2026-100588 | 09/26/2026 | 8.3 | High | Authorisation flaw | 2026.7.1 |
| CVE-2026-100589 | 09/26/2026 | 8.3 | High | Authorisation flaw | 2026.7.1 |
| CVE-2026-100567 | 09/26/2026 | 8.2 | High | Server-side request forgery | Not stated |
| CVE-2026-100559 | 09/26/2026 | 8 | High | Command execution or injection | 2026.8.1 |
| CVE-2026-100561 | 09/26/2026 | 8 | High | Command execution or injection | Not stated |
| CVE-2026-100585 | 09/26/2026 | 8 | High | Authorisation flaw | 2026.7.1 |
| CVE-2026-100570 | 09/26/2026 | 7.8 | High | Command execution or injection | Not stated |
| CVE-2026-100597 | 09/26/2026 | 7.8 | High | Race condition | 2026.7.1 |
| CVE-2026-100578 | 09/26/2026 | 7.6 | High | Authorisation flaw | 2026.7.1 |
| CVE-2026-100579 | 09/26/2026 | 7.6 | High | Authorisation flaw | 2026.7.1 |
| CVE-2026-100535 | 09/26/2026 | 7.5 | High | Authorisation flaw | Not stated |
| CVE-2026-100541 | 09/26/2026 | 7.5 | High | Other | Not stated |
| CVE-2026-100543 | 09/26/2026 | 7.5 | High | Information exposure | 2026.8.1 |
| CVE-2026-100558 | 09/26/2026 | 7.5 | High | Resource exhaustion | 2026.8.1 |
| CVE-2026-100560 | 09/26/2026 | 7.5 | High | Authorisation flaw | 2026.8.1 |
| CVE-2026-100530 | 09/26/2026 | 7.3 | High | Authorisation flaw | 2026.8.1 |
| CVE-2026-100555 | 09/26/2026 | 7.1 | High | Server-side request forgery | Not stated |
| CVE-2026-100598 | 09/26/2026 | 7.1 | High | Authentication flaw | 2026.7.1 |
| CVE-2026-100540 | 09/26/2026 | 6.8 | Medium | Authorisation flaw | 2026.8.1 |
| CVE-2026-100584 | 09/26/2026 | 6.7 | Medium | Command execution or injection | Not stated |
| CVE-2026-100536 | 09/26/2026 | 6.5 | Medium | Path traversal | 2026.8.1 |
| CVE-2026-100538 | 09/26/2026 | 6.5 | Medium | Authorisation flaw | 2026.8.1 |
| CVE-2026-100566 | 09/26/2026 | 6.5 | Medium | Authorisation flaw | 2026.8.1 |
| CVE-2026-100582 | 09/26/2026 | 6.5 | Medium | Authorisation flaw | 2026.8.1 |
| CVE-2026-100594 | 09/26/2026 | 6.5 | Medium | Information exposure | 2026.7.1 |
| CVE-2026-100595 | 09/26/2026 | 6.5 | Medium | Information exposure | 2026.7.1 |
| CVE-2026-100602 | 09/26/2026 | 6.5 | Medium | Authorisation flaw | Not stated |
| CVE-2026-100529 | 09/26/2026 | 6.4 | Medium | Authorisation flaw | 2026.8.1 |
| CVE-2026-100546 | 09/26/2026 | 6.4 | Medium | Race condition | Not stated |
| CVE-2026-100556 | 09/26/2026 | 6.3 | Medium | Authorisation flaw | Not stated |
| CVE-2026-100577 | 09/26/2026 | 6.3 | Medium | Server-side request forgery | 2026.8.1 |
| CVE-2026-100591 | 09/26/2026 | 6.3 | Medium | Authorisation flaw | 2026.7.1 |
| CVE-2026-100592 | 09/26/2026 | 6.3 | Medium | Authorisation flaw | Not stated |
| CVE-2026-100574 | 09/26/2026 | 5.9 | Medium | Server-side request forgery | 2026.8.1 |
| CVE-2026-100547 | 09/26/2026 | 5.5 | Medium | Other | Not stated |
| CVE-2026-100569 | 09/26/2026 | 5.5 | Medium | Authentication flaw | Not stated |
| CVE-2026-100581 | 09/26/2026 | 5.5 | Medium | Information exposure | 2026.8.11 |
| CVE-2026-100528 | 09/26/2026 | 5.4 | Medium | Information exposure | 2026.8.1 |
| CVE-2026-100549 | 09/26/2026 | 5.4 | Medium | Path traversal | 2026.8.1 |
| CVE-2026-100550 | 09/26/2026 | 5.4 | Medium | Authorisation flaw | 2026.8.1 |
| CVE-2026-100562 | 09/26/2026 | 5.4 | Medium | Authorisation flaw | 2026.8.1 |
| CVE-2026-100563 | 09/26/2026 | 5.4 | Medium | Other | 2026.8.1 |
| CVE-2026-100564 | 09/26/2026 | 5.4 | Medium | Other | 2026.8.1 |
| CVE-2026-100576 | 09/26/2026 | 5.4 | Medium | Server-side request forgery | 2026.8.1 |
| CVE-2026-100593 | 09/26/2026 | 5.4 | Medium | Authorisation flaw | 2026.7.1 |
| CVE-2026-100603 | 09/26/2026 | 5.4 | Medium | Other | Not stated |
| CVE-2026-100604 | 09/26/2026 | 5.4 | Medium | Authorisation flaw | Not stated |
| CVE-2026-100526 | 09/26/2026 | 5.3 | Medium | Authorisation flaw | 2026.9.3 |
| CVE-2026-100527 | 09/26/2026 | 5.3 | Medium | Resource exhaustion | 2026.8.2 |
| CVE-2026-100533 | 09/26/2026 | 5.3 | Medium | Path traversal | 2026.8.1 |
| CVE-2026-100545 | 09/26/2026 | 5.3 | Medium | Authorisation flaw | 2026.8.1 |
| CVE-2026-100548 | 09/26/2026 | 5.3 | Medium | Information exposure | Not stated |
| CVE-2026-100571 | 09/26/2026 | 5.3 | Medium | Resource exhaustion | Not stated |
| CVE-2026-100572 | 09/26/2026 | 5.3 | Medium | Resource exhaustion | Not stated |
| CVE-2026-100600 | 09/26/2026 | 5.3 | Medium | Resource exhaustion | Not stated |
| CVE-2026-100601 | 09/26/2026 | 5.3 | Medium | Server-side request forgery | Not stated |
| CVE-2026-100525 | 09/26/2026 | 4.3 | Medium | Authorisation flaw | 2026.9.3 |
| CVE-2026-100553 | 09/26/2026 | 4.3 | Medium | Authorisation flaw | Not stated |
| CVE-2026-100583 | 09/26/2026 | 4.3 | Medium | Authorisation flaw | 2026.7.1 |
| CVE-2026-100590 | 09/26/2026 | 4.3 | Medium | Authorisation flaw | 2026.7.1 |
| CVE-2026-100554 | 09/26/2026 | 4.2 | Medium | Authentication flaw | Not stated |
| CVE-2026-100573 | 09/26/2026 | 3.3 | Low | Authorisation flaw | 2026.8.1 |
| CVE-2026-100534 | 09/26/2026 | 3.1 | Low | Authorisation flaw | 2026.8.1 |
| CVE-2026-100537 | 09/26/2026 | 3.1 | Low | Authorisation flaw | 2026.8.1 |
| CVE-2026-100542 | 09/26/2026 | 3.1 | Low | Resource exhaustion | Not stated |
| CVE-2026-100539 | 09/26/2026 | 2.6 | Low | Authorisation flaw | 2026.8.1 |
| CVE-2026-95815 | 09/22/2026 | 6.3 | Medium | Information exposure | 2026.8.11 |
| CVE-2026-94094 | 09/20/2026 | 4.3 | Medium | Other | Not stated |
| CVE-2026-91835 | 09/15/2026 | 2.8 | Low | Other | Not stated |
| CVE-2026-91836 | 09/15/2026 | 2.8 | Low | Other | Not stated |
| CVE-2026-90818 | 09/14/2026 | 4.3 | Medium | Server-side request forgery | Not stated |
| CVE-2026-19006 | 08/06/2026 | 6.3 | Medium | Authorisation flaw | Not stated |
| CVE-2026-19007 | 08/06/2026 | 6.3 | Medium | Authorisation flaw | Not stated |
| CVE-2026-19008 | 08/06/2026 | 6.3 | Medium | Path traversal | Not stated |
| CVE-2026-66418 | 07/30/2026 | 9.3 | Critical | Command execution or injection | Not stated |
| CVE-2026-66421 | 07/30/2026 | 9.3 | Critical | Command execution or injection | Not stated |
| CVE-2026-17458 | 07/26/2026 | 6.3 | Medium | Server-side request forgery | Not stated |
| CVE-2026-17457 | 07/26/2026 | 4.3 | Medium | Information exposure | Not stated |
| CVE-2026-62202 | 07/17/2026 | 8.8 | High | Authorisation flaw | 2026.6.9 |
| CVE-2026-62203 | 07/17/2026 | 8.8 | High | Command execution or injection | 2026.6.6 |
| CVE-2026-62207 | 07/17/2026 | 8.8 | High | Authorisation flaw | 2026.6.5 |
| CVE-2026-62217 | 07/17/2026 | 8.8 | High | Authorisation flaw | 2026.5.27 |
| CVE-2026-62218 | 07/17/2026 | 8.8 | High | Authorisation flaw | 2026.5.27 |
| CVE-2026-62223 | 07/17/2026 | 8.8 | High | Authorisation flaw | 2026.5.18 |
| CVE-2026-62228 | 07/17/2026 | 8.8 | High | Authorisation flaw | 2026.6.5 |
| CVE-2026-62229 | 07/17/2026 | 8.8 | High | Path traversal | 2026.5.18 |
| CVE-2026-62226 | 07/17/2026 | 8.5 | High | Server-side request forgery | 2026.5.19 |
| CVE-2026-62209 | 07/17/2026 | 8.1 | High | Authorisation flaw | 2026.6.5 |
| CVE-2026-62215 | 07/17/2026 | 8 | High | Authentication flaw | 2026.6.5 |
| CVE-2026-62222 | 07/17/2026 | 7.8 | High | Command execution or injection | 2026.5.22 |
| CVE-2026-62201 | 07/17/2026 | 7.7 | High | Server-side request forgery | 2026.6.6 |
| CVE-2026-62227 | 07/17/2026 | 7.7 | High | Server-side request forgery | 2026.5.26 |
| CVE-2026-62205 | 07/17/2026 | 7.1 | High | Authorisation flaw | 2026.6.6 |
| CVE-2026-62206 | 07/17/2026 | 7.1 | High | Authorisation flaw | 2026.6.9 |
| CVE-2026-62212 | 07/17/2026 | 7.1 | High | Race condition | 2026.5.28 |
| CVE-2026-62219 | 07/17/2026 | 7.1 | High | Authorisation flaw | 2026.5.26 |
| CVE-2026-62208 | 07/17/2026 | 6.5 | Medium | Authentication flaw | 2026.6.5 |
| CVE-2026-62210 | 07/17/2026 | 6.5 | Medium | Resource exhaustion | 2026.6.1 |
| CVE-2026-62213 | 07/17/2026 | 6.5 | Medium | Authentication flaw | 2026.5.27 |
| CVE-2026-62214 | 07/17/2026 | 6.5 | Medium | Authentication flaw | 2026.5.28 |
| CVE-2026-62221 | 07/17/2026 | 5.4 | Medium | Authorisation flaw | 2026.5.26 |
| CVE-2026-62224 | 07/17/2026 | 5.4 | Medium | Authentication flaw | 2026.5.12 |
| CVE-2026-62225 | 07/17/2026 | 5.4 | Medium | Authorisation flaw | 2026.5.18 |
| CVE-2026-62220 | 07/17/2026 | 5.3 | Medium | Authentication flaw | 2026.5.26 |
| CVE-2026-62211 | 07/17/2026 | 5 | Medium | Information exposure | 2026.6.1 |
| CVE-2026-62216 | 07/17/2026 | 5 | Medium | Server-side request forgery | 2026.5.28 |
| CVE-2026-62190 | 07/13/2026 | 8.8 | High | Path traversal | 2026.6.9 |
| CVE-2026-62194 | 07/13/2026 | 8.8 | High | Authorisation flaw | 2026.6.9 |
| CVE-2026-62199 | 07/13/2026 | 8.8 | High | Command execution or injection | 2026.6.6 |
| CVE-2026-62200 | 07/13/2026 | 8.8 | High | Command execution or injection | 2026.6.6 |
| CVE-2026-62197 | 07/13/2026 | 8.5 | High | Server-side request forgery | 2026.6.6 |
| CVE-2026-62195 | 07/13/2026 | 8.3 | High | Authorisation flaw | 2026.6.6 |
| CVE-2026-62196 | 07/13/2026 | 8.3 | High | Authorisation flaw | 2026.6.6 |
| CVE-2026-62187 | 07/13/2026 | 8.1 | High | Authorisation flaw | Not stated |
| CVE-2026-62188 | 07/13/2026 | 8.1 | High | Authorisation flaw | Not stated |
| CVE-2026-62192 | 07/13/2026 | 8.1 | High | Authorisation flaw | 2026.6.9 |
| CVE-2026-62186 | 07/13/2026 | 7.6 | High | Authorisation flaw | 2026.6.8 |
| CVE-2026-62189 | 07/13/2026 | 7.1 | High | Path traversal | 2026.6.9 |
| CVE-2026-62191 | 07/13/2026 | 7.1 | High | Authorisation flaw | 2026.6.9 |
| CVE-2026-62193 | 07/13/2026 | 4.9 | Medium | Authorisation flaw | 2026.6.9 |
| CVE-2026-62198 | 07/13/2026 | 4.3 | Medium | Authorisation flaw | 2026.6.6 |
| CVE-2026-15193 | 07/09/2026 | 5.3 | Medium | Command execution or injection | Not stated |
| CVE-2026-59261 | 07/08/2026 | 7.1 | High | Command execution or injection | 2026.5.28 |
| CVE-2026-55249 | 06/23/2026 | 6.3 | Medium | Command execution or injection | Not stated |
| CVE-2026-53843 | 06/16/2026 | 8.8 | High | Authentication flaw | 2026.5.26 |
| CVE-2026-53853 | 06/16/2026 | 8.3 | High | Authorisation flaw | 2026.5.12 |
| CVE-2026-53849 | 06/16/2026 | 8.1 | High | Authentication flaw | 2026.5.7 |
| CVE-2026-53855 | 06/16/2026 | 8.1 | High | Command execution or injection | 2026.4.2 |
| CVE-2026-53857 | 06/16/2026 | 8.1 | High | Authentication flaw | 2026.5.3 |
| CVE-2026-53864 | 06/16/2026 | 8.1 | High | Command execution or injection | 2026.5.26 |
| CVE-2026-53866 | 06/16/2026 | 8.1 | High | Authorisation flaw | 2026.5.12 |
| CVE-2026-53840 | 06/16/2026 | 7.1 | High | Authentication flaw | 2026.5.12 |
| CVE-2026-53842 | 06/16/2026 | 7.1 | High | Command execution or injection | 2026.5.2 |
| CVE-2026-53846 | 06/16/2026 | 7.1 | High | Command execution or injection | 2026.4.29 |
| CVE-2026-53858 | 06/16/2026 | 7.1 | High | Command execution or injection | 2026.5.2 |
| CVE-2026-53863 | 06/16/2026 | 7.1 | High | Authorisation flaw | 2026.4.25 |
| CVE-2026-53865 | 06/16/2026 | 7.1 | High | Command execution or injection | 2026.5.2 |
| CVE-2026-53861 | 06/16/2026 | 6.6 | Medium | Command execution or injection | 2026.5.6 |
| CVE-2026-53844 | 06/16/2026 | 6.5 | Medium | Authorisation flaw | 2026.4.29 |
| CVE-2026-53854 | 06/16/2026 | 6.5 | Medium | Authorisation flaw | 2026.4.25 |
| CVE-2026-53859 | 06/16/2026 | 6.5 | Medium | Server-side request forgery | 2026.5.26 |
| CVE-2026-53841 | 06/16/2026 | 6.1 | Medium | Other | 2026.5.12 |
| CVE-2026-53850 | 06/16/2026 | 5.5 | Medium | Authorisation flaw | 2026.4.25 |
| CVE-2026-53856 | 06/16/2026 | 5.5 | Medium | Authorisation flaw | 2026.4.24 |
| CVE-2026-53847 | 06/16/2026 | 5.4 | Medium | Authorisation flaw | 2026.5.6 |
| CVE-2026-53852 | 06/16/2026 | 5.4 | Medium | Authentication flaw | 2026.4.25 |
| CVE-2026-53851 | 06/16/2026 | 5.3 | Medium | Authorisation flaw | 2026.5.12 |
| CVE-2026-53845 | 06/16/2026 | 4.3 | Medium | Other | 2026.5.6 |
| CVE-2026-53848 | 06/16/2026 | 4.3 | Medium | Command execution or injection | 2026.5.26 |
| CVE-2026-53860 | 06/16/2026 | 4.2 | Medium | Command execution or injection | 2026.5.7 |
| CVE-2026-53862 | 06/16/2026 | 4.2 | Medium | Authorisation flaw | 2026.5.12 |
| CVE-2026-53838 | 06/12/2026 | 9.8 | Critical | Race condition | 2026.5.27 |
| CVE-2026-53821 | 06/12/2026 | 8.8 | High | Authorisation flaw | 2026.5.18 |
| CVE-2026-53822 | 06/12/2026 | 8.8 | High | Race condition | 2026.5.18 |
| CVE-2026-53828 | 06/12/2026 | 8.8 | High | Authorisation flaw | 2026.5.6 |
| CVE-2026-53836 | 06/12/2026 | 8.8 | High | Command execution or injection | 2026.5.12 |
| CVE-2026-53831 | 06/12/2026 | 8.3 | High | Race condition | 2026.5.18 |
| CVE-2026-53823 | 06/12/2026 | 8.1 | High | Authentication flaw | 2026.5.3 |
| CVE-2026-53829 | 06/12/2026 | 8 | High | Other | 2026.5.18 |
| CVE-2026-53832 | 06/12/2026 | 7.7 | High | Authentication flaw | 2026.5.18 |
| CVE-2026-53833 | 06/12/2026 | 7.7 | High | Authentication flaw | 2026.4.29 |
| CVE-2026-53834 | 06/12/2026 | 7.5 | High | Authorisation flaw | 2026.4.27 |
| CVE-2026-53820 | 06/12/2026 | 6.6 | Medium | Authorisation flaw | 2026.5.12 |
| CVE-2026-53824 | 06/12/2026 | 6.5 | Medium | Authentication flaw | 2026.4.24 |
| CVE-2026-53825 | 06/12/2026 | 6.5 | Medium | Path traversal | 2026.4.7 |
| CVE-2026-53827 | 06/12/2026 | 6.5 | Medium | Server-side request forgery | 2026.5.2 |
| CVE-2026-53830 | 06/12/2026 | 6.5 | Medium | Authentication flaw | 2026.4.22 |
| CVE-2026-53839 | 06/12/2026 | 6.5 | Medium | Other | 2026.5.7 |
| CVE-2026-53826 | 06/12/2026 | 4.3 | Medium | Authorisation flaw | 2026.4.26 |
| CVE-2026-53835 | 06/12/2026 | 4.3 | Medium | Authorisation flaw | 2026.5.6 |
| CVE-2026-53837 | 06/12/2026 | 3.7 | Low | Authentication flaw | 2026.5.6 |
| CVE-2026-53806 | 06/11/2026 | 8.8 | High | Race condition | 2026.5.12 |
| CVE-2026-53807 | 06/11/2026 | 8.8 | High | Authorisation flaw | 2026.5.6 |
| CVE-2026-53810 | 06/11/2026 | 8.8 | High | Command execution or injection | 2026.5.18 |
| CVE-2026-53811 | 06/11/2026 | 8.8 | High | Authentication flaw | 2026.5.7 |
| CVE-2026-53817 | 06/11/2026 | 8.8 | High | Authentication flaw | 2026.5.22 |
| CVE-2026-53819 | 06/11/2026 | 8.8 | High | Command execution or injection | 2026.5.27 |
| CVE-2026-53814 | 06/11/2026 | 8.3 | High | Authorisation flaw | 2026.5.20 |
| CVE-2026-53813 | 06/11/2026 | 7.8 | High | Other | 2026.4.25 |
| CVE-2026-53812 | 06/11/2026 | 7.7 | High | Server-side request forgery | 2026.5.18 |
| CVE-2026-53816 | 06/11/2026 | 7.2 | High | Authorisation flaw | 2026.5.18 |
| CVE-2026-53818 | 06/11/2026 | 6.6 | Medium | Authorisation flaw | 2026.4.24 |
| CVE-2026-53808 | 06/11/2026 | 6.5 | Medium | Authorisation flaw | 2026.5.6 |
| CVE-2026-53815 | 06/11/2026 | 6.5 | Medium | Authorisation flaw | 2026.5.19 |
| CVE-2026-53809 | 06/11/2026 | 3.8 | Low | Authorisation flaw | 2026.4.25 |
| CVE-2026-35674 | 05/29/2026 | 8.8 | High | Authorisation flaw | 2026.5.18 |
| CVE-2026-32905 | 05/29/2026 | 8.3 | High | Authorisation flaw | 2026.5.4 |
| CVE-2026-35630 | 05/29/2026 | 8 | High | Authorisation flaw | 2026.5.18 |
| CVE-2026-35673 | 05/29/2026 | 6.5 | Medium | Authorisation flaw | 2026.4.29 |
| CVE-2026-34507 | 05/29/2026 | 5.4 | Medium | Authorisation flaw | 2026.4.29 |
| CVE-2026-32906 | 05/29/2026 | 4.3 | Medium | Authorisation flaw | 2026.5.12 |
| CVE-2026-45006 | 05/11/2026 | 8.8 | High | Command execution or injection | 2026.4.23 |
| CVE-2026-45004 | 05/11/2026 | 7.8 | High | Other | 2026.4.23 |
| CVE-2026-44995 | 05/11/2026 | 7.3 | High | Command execution or injection | 2026.4.20 |
| CVE-2026-8305 | 05/11/2026 | 7.3 | High | Authentication flaw | Not stated |
| CVE-2026-45001 | 05/11/2026 | 7.1 | High | Authorisation flaw | 2026.4.20 |
| CVE-2026-45005 | 05/11/2026 | 6 | Medium | Other | 2026.4.23 |
| CVE-2026-44993 | 05/11/2026 | 5.4 | Medium | Command execution or injection | 2026.4.20 |
| CVE-2026-44998 | 05/11/2026 | 5.4 | Medium | Authorisation flaw | 2026.4.20 |
| CVE-2026-44994 | 05/11/2026 | 5.3 | Medium | Authorisation flaw | 2026.4.22 |
| CVE-2026-44999 | 05/11/2026 | 5.3 | Medium | Authentication flaw | 2026.4.20 |
| CVE-2026-45002 | 05/11/2026 | 5.3 | Medium | Authorisation flaw | 2026.4.20 |
| CVE-2026-44992 | 05/11/2026 | 5 | Medium | Other | 2026.4.20 |
| CVE-2026-45000 | 05/11/2026 | 5 | Medium | Server-side request forgery | 2026.4.20 |
| CVE-2026-45003 | 05/11/2026 | 5 | Medium | Other | 2026.4.22 |
| CVE-2026-44997 | 05/11/2026 | 4.3 | Medium | Authorisation flaw | 2026.4.22 |
| CVE-2026-44991 | 05/11/2026 | 4.2 | Medium | Authorisation flaw | 2026.4.21 |
| CVE-2026-44996 | 05/11/2026 | 3.7 | Low | Path traversal | 2026.4.15 |
| CVE-2026-43575 | 05/06/2026 | 9.8 | Critical | Authorisation flaw | 2026.4.10 |
| CVE-2026-44109 | 05/06/2026 | 9.8 | Critical | Other | 2026.4.15 |
| CVE-2026-43581 | 05/06/2026 | 9.6 | Critical | Other | 2026.4.10 |
| CVE-2026-44112 | 05/06/2026 | 9.6 | Critical | Race condition | 2026.4.22 |
| CVE-2026-43578 | 05/06/2026 | 9.1 | Critical | Command execution or injection | 2026.4.10 |
| CVE-2026-43584 | 05/06/2026 | 8.8 | High | Command execution or injection | 2026.4.10 |
| CVE-2026-44110 | 05/06/2026 | 8.8 | High | Authorisation flaw | 2026.4.15 |
| CVE-2026-44115 | 05/06/2026 | 8.8 | High | Command execution or injection | 2026.4.22 |
| CVE-2026-44116 | 05/06/2026 | 8.6 | High | Server-side request forgery | 2026.4.22 |
| CVE-2026-43585 | 05/06/2026 | 8.1 | High | Other | 2026.4.15 |
| CVE-2026-44114 | 05/06/2026 | 7.8 | High | Command execution or injection | 2026.4.20 |
| CVE-2026-44118 | 05/06/2026 | 7.8 | High | Authentication flaw | 2026.4.22 |
| CVE-2026-43576 | 05/06/2026 | 7.7 | High | Server-side request forgery | 2026.4.5 |
| CVE-2026-43580 | 05/06/2026 | 7.7 | High | Authorisation flaw | 2026.4.10 |
| CVE-2026-44113 | 05/06/2026 | 7.7 | High | Race condition | 2026.4.22 |
| CVE-2026-43577 | 05/06/2026 | 6.5 | Medium | Authorisation flaw | 2026.4.9 |
| CVE-2026-43579 | 05/06/2026 | 6.5 | Medium | Authorisation flaw | 2026.4.10 |
| CVE-2026-43582 | 05/06/2026 | 6.3 | Medium | Race condition | 2026.4.10 |
| CVE-2026-44117 | 05/06/2026 | 5.8 | Medium | Server-side request forgery | 2026.4.20 |
| CVE-2026-43583 | 05/06/2026 | 5.3 | Medium | Authorisation flaw | 2026.4.14 |
| CVE-2026-44111 | 05/06/2026 | 4.3 | Medium | Other | 2026.4.15 |
| CVE-2026-43534 | 05/05/2026 | 9.1 | Critical | Authentication flaw | 2026.4.10 |
| CVE-2026-43566 | 05/05/2026 | 9.1 | Critical | Command execution or injection | 2026.4.14 |
| CVE-2026-42434 | 05/05/2026 | 8.8 | High | Authorisation flaw | 2026.4.10 |
| CVE-2026-42435 | 05/05/2026 | 8.8 | High | Command execution or injection | 2026.4.12 |
| CVE-2026-43530 | 05/05/2026 | 8.8 | High | Authorisation flaw | 2026.4.12 |
| CVE-2026-43569 | 05/05/2026 | 8.8 | High | Command execution or injection | 2026.4.9 |
| CVE-2026-43571 | 05/05/2026 | 8.8 | High | Command execution or injection | 2026.4.10 |
| CVE-2026-43533 | 05/05/2026 | 8.6 | High | Path traversal | 2026.4.10 |
| CVE-2026-42439 | 05/05/2026 | 8.5 | High | Authorisation flaw | 2026.4.10 |
| CVE-2026-43526 | 05/05/2026 | 8.2 | High | Server-side request forgery | 2026.4.12 |
| CVE-2026-42436 | 05/05/2026 | 7.7 | High | Authorisation flaw | 2026.4.14 |
| CVE-2026-42438 | 05/05/2026 | 7.7 | High | Authorisation flaw | 2026.4.10 |
| CVE-2026-43527 | 05/05/2026 | 7.7 | High | Server-side request forgery | 2026.4.14 |
| CVE-2026-43532 | 05/05/2026 | 7.7 | High | Command execution or injection | 2026.4.10 |
| CVE-2026-43573 | 05/05/2026 | 7.7 | High | Authorisation flaw | 2026.4.10 |
| CVE-2026-42437 | 05/05/2026 | 7.5 | High | Resource exhaustion | 2026.4.10 |
| CVE-2026-43531 | 05/05/2026 | 7.3 | High | Other | 2026.4.9 |
| CVE-2026-43535 | 05/05/2026 | 6.8 | Medium | Authorisation flaw | 2026.4.14 |
| CVE-2026-42433 | 05/05/2026 | 6.5 | Medium | Authorisation flaw | 2026.4.10 |
| CVE-2026-43528 | 05/05/2026 | 6.5 | Medium | Other | 2026.4.14 |
| CVE-2026-43567 | 05/05/2026 | 6.5 | Medium | Authorisation flaw | 2026.4.10 |
| CVE-2026-43568 | 05/05/2026 | 6.5 | Medium | Authorisation flaw | 2026.4.10 |
| CVE-2026-43570 | 05/05/2026 | 6.5 | Medium | Other | 2026.4.5 |
| CVE-2026-43574 | 05/05/2026 | 6.5 | Medium | Other | 2026.4.12 |
| CVE-2026-43572 | 05/05/2026 | 5.3 | Medium | Authorisation flaw | 2026.4.14 |
| CVE-2026-43529 | 05/05/2026 | 2.5 | Low | Race condition | 2026.4.10 |
| CVE-2026-41386 | 04/28/2026 | 9.1 | Critical | Authorisation flaw | 2026.3.22 |
| CVE-2026-41378 | 04/28/2026 | 8.8 | High | Authorisation flaw | 2026.3.31 |
| CVE-2026-41404 | 04/28/2026 | 8.8 | High | Authorisation flaw | 2026.3.31 |
| CVE-2026-42422 | 04/28/2026 | 8.8 | High | Authorisation flaw | 2026.4.8 |
| CVE-2026-42426 | 04/28/2026 | 8.8 | High | Authorisation flaw | 2026.4.8 |
| CVE-2026-41371 | 04/28/2026 | 8.5 | High | Authorisation flaw | 2026.3.28 |
| CVE-2026-41914 | 04/28/2026 | 8.5 | High | Server-side request forgery | 2026.4.8 |
| CVE-2026-41394 | 04/28/2026 | 8.2 | High | Authorisation flaw | 2026.3.31 |
| CVE-2026-41364 | 04/28/2026 | 8.1 | High | Path traversal | 2026.3.31 |
| CVE-2026-41383 | 04/28/2026 | 8.1 | High | Path traversal | 2026.4.2 |
| CVE-2026-42431 | 04/28/2026 | 8.1 | High | Authorisation flaw | 2026.4.8 |
| CVE-2026-41384 | 04/28/2026 | 7.8 | High | Other | 2026.3.24 |
| CVE-2026-41387 | 04/28/2026 | 7.8 | High | Other | 2026.3.22 |
| CVE-2026-41396 | 04/28/2026 | 7.8 | High | Command execution or injection | 2026.3.31 |
| CVE-2026-42432 | 04/28/2026 | 7.8 | High | Authorisation flaw | 2026.4.8 |
| CVE-2026-41912 | 04/28/2026 | 7.6 | High | Server-side request forgery | 2026.4.8 |
| CVE-2026-41395 | 04/28/2026 | 7.5 | High | Other | 2026.3.28 |
| CVE-2026-41399 | 04/28/2026 | 7.5 | High | Resource exhaustion | 2026.3.28 |
| CVE-2026-41405 | 04/28/2026 | 7.5 | High | Other | 2026.3.31 |
| CVE-2026-42423 | 04/28/2026 | 7.5 | High | Authentication flaw | 2026.4.8 |
| CVE-2026-41380 | 04/28/2026 | 7.3 | High | Command execution or injection | 2026.3.28 |
| CVE-2026-41390 | 04/28/2026 | 7.3 | High | Command execution or injection | 2026.3.28 |
| CVE-2026-41379 | 04/28/2026 | 7.1 | High | Authorisation flaw | 2026.3.28 |
| CVE-2026-42428 | 04/28/2026 | 7.1 | High | Other | 2026.4.8 |
| CVE-2026-42429 | 04/28/2026 | 7.1 | High | Authorisation flaw | 2026.4.8 |
| CVE-2026-41397 | 04/28/2026 | 6.8 | Medium | Path traversal | 2026.3.31 |
| CVE-2026-41392 | 04/28/2026 | 6.7 | Medium | Command execution or injection | 2026.3.31 |
| CVE-2026-41368 | 04/28/2026 | 6.5 | Medium | Authorisation flaw | 2026.3.28 |
| CVE-2026-41369 | 04/28/2026 | 6.5 | Medium | Authorisation flaw | 2026.3.31 |
| CVE-2026-41370 | 04/28/2026 | 6.5 | Medium | Path traversal | 2026.3.31 |
| CVE-2026-41375 | 04/28/2026 | 6.5 | Medium | Authorisation flaw | 2026.3.28 |
| CVE-2026-41385 | 04/28/2026 | 6.5 | Medium | Information exposure | 2026.3.31 |
| CVE-2026-41388 | 04/28/2026 | 6.5 | Medium | Other | 2026.3.31 |
| CVE-2026-41911 | 04/28/2026 | 6.5 | Medium | Path traversal | 2026.4.8 |
| CVE-2026-42430 | 04/28/2026 | 6.5 | Medium | Server-side request forgery | 2026.4.8 |
| CVE-2026-41373 | 04/28/2026 | 6.1 | Medium | Other | 2026.3.31 |
| CVE-2026-41372 | 04/28/2026 | 5.8 | Medium | Authorisation flaw | 2026.4.2 |
| CVE-2026-42424 | 04/28/2026 | 5.7 | Medium | Path traversal | 2026.4.8 |
| CVE-2026-41366 | 04/28/2026 | 5.5 | Medium | Authorisation flaw | 2026.3.31 |
| CVE-2026-41365 | 04/28/2026 | 5.4 | Medium | Other | 2026.3.31 |
| CVE-2026-41376 | 04/28/2026 | 5.4 | Medium | Authentication flaw | 2026.3.31 |
| CVE-2026-41381 | 04/28/2026 | 5.4 | Medium | Authorisation flaw | 2026.3.31 |
| CVE-2026-41382 | 04/28/2026 | 5.4 | Medium | Authorisation flaw | 2026.3.31 |
| CVE-2026-41406 | 04/28/2026 | 5.4 | Medium | Authorisation flaw | 2026.3.31 |
| CVE-2026-41916 | 04/28/2026 | 5.4 | Medium | Authentication flaw | 2026.4.8 |
| CVE-2026-42421 | 04/28/2026 | 5.4 | Medium | Authentication flaw | 2026.4.8 |
| CVE-2026-41363 | 04/28/2026 | 5.3 | Medium | Path traversal | Not stated |
| CVE-2026-41374 | 04/28/2026 | 5.3 | Medium | Other | 2026.3.31 |
| CVE-2026-41391 | 04/28/2026 | 5.3 | Medium | Command execution or injection | 2026.3.31 |
| CVE-2026-41400 | 04/28/2026 | 5.3 | Medium | Resource exhaustion | 2026.3.31 |
| CVE-2026-41915 | 04/28/2026 | 5.3 | Medium | Command execution or injection | 2026.4.8 |
| CVE-2026-42427 | 04/28/2026 | 5.3 | Medium | Command execution or injection | 2026.4.8 |
| CVE-2026-41367 | 04/28/2026 | 5 | Medium | Authorisation flaw | Not stated |
| CVE-2026-41393 | 04/28/2026 | 4.8 | Medium | Authentication flaw | 2026.3.31 |
| CVE-2026-41377 | 04/28/2026 | 4.6 | Medium | Authentication flaw | 2026.3.31 |
| CVE-2026-41398 | 04/28/2026 | 4.6 | Medium | Authentication flaw | 2026.4.2 |
| CVE-2026-41362 | 04/28/2026 | 4.3 | Medium | Authorisation flaw | 2026.3.31 |
| CVE-2026-41408 | 04/28/2026 | 4.3 | Medium | Resource exhaustion | 2026.3.31 |
| CVE-2026-41910 | 04/28/2026 | 4.3 | Medium | Authorisation flaw | 2026.4.8 |
| CVE-2026-42420 | 04/28/2026 | 4.3 | Medium | Resource exhaustion | 2026.4.8 |
| CVE-2026-41402 | 04/28/2026 | 4.2 | Medium | Path traversal | 2026.3.31 |
| CVE-2026-41407 | 04/28/2026 | 3.7 | Low | Other | 2026.4.2 |
| CVE-2026-41913 | 04/28/2026 | 3.7 | Low | Race condition | 2026.4.4 |
| CVE-2026-41403 | 04/28/2026 | 2.9 | Low | Command execution or injection | 2026.3.31 |
| CVE-2026-41349 | 04/23/2026 | 8.8 | High | Authorisation flaw | 2026.3.28 |
| CVE-2026-41352 | 04/23/2026 | 8.8 | High | Authorisation flaw | 2026.3.31 |
| CVE-2026-41353 | 04/23/2026 | 8.1 | High | Other | 2026.3.22 |
| CVE-2026-41336 | 04/23/2026 | 7.8 | High | Command execution or injection | 2026.3.31 |
| CVE-2026-41342 | 04/23/2026 | 7.3 | High | Authentication flaw | 2026.3.28 |
| CVE-2026-41355 | 04/23/2026 | 7.3 | High | Command execution or injection | 2026.3.28 |
| CVE-2026-41347 | 04/23/2026 | 7.1 | High | Other | 2026.3.31 |
| CVE-2026-41359 | 04/23/2026 | 7.1 | High | Authorisation flaw | 2026.3.28 |
| CVE-2026-41361 | 04/23/2026 | 7.1 | High | Command execution or injection | 2026.3.28 |
| CVE-2026-41360 | 04/23/2026 | 6.7 | Medium | Race condition | 2026.4.2 |
| CVE-2026-41334 | 04/23/2026 | 6.5 | Medium | Authentication flaw | 2026.3.31 |
| CVE-2026-41340 | 04/23/2026 | 6.5 | Medium | Other | 2026.3.31 |
| CVE-2026-41909 | 04/23/2026 | 5.4 | Medium | Authorisation flaw | 2026.4.20 |
| CVE-2026-41341 | 04/23/2026 | 5.4 | Medium | Other | 2026.3.31 |
| CVE-2026-41344 | 04/23/2026 | 5.4 | Medium | Authorisation flaw | 2026.3.28 |
| CVE-2026-41348 | 04/23/2026 | 5.4 | Medium | Authorisation flaw | 2026.3.31 |
| CVE-2026-41356 | 04/23/2026 | 5.4 | Medium | Authentication flaw | 2026.3.31 |
| CVE-2026-41358 | 04/23/2026 | 5.4 | Medium | Authentication flaw | 2026.4.2 |
| CVE-2026-41332 | 04/23/2026 | 5.3 | Medium | Command execution or injection | 2026.3.28 |
| CVE-2026-41335 | 04/23/2026 | 5.3 | Medium | Other | 2026.3.31 |
| CVE-2026-41337 | 04/23/2026 | 5.3 | Medium | Race condition | 2026.3.31 |
| CVE-2026-41343 | 04/23/2026 | 5.3 | Medium | Other | 2026.3.31 |
| CVE-2026-41345 | 04/23/2026 | 5.3 | Medium | Authentication flaw | 2026.3.31 |
| CVE-2026-41346 | 04/23/2026 | 5.3 | Medium | Other | 2026.3.31 |
| CVE-2026-41351 | 04/23/2026 | 5.3 | Medium | Other | 2026.3.31 |
| CVE-2026-41338 | 04/23/2026 | 5 | Medium | Race condition | 2026.3.31 |
| CVE-2026-41908 | 04/23/2026 | 4.3 | Medium | Authorisation flaw | 2026.4.20 |
| CVE-2026-41339 | 04/23/2026 | 4.3 | Medium | Other | 2026.4.2 |
| CVE-2026-41350 | 04/23/2026 | 4.3 | Medium | Authorisation flaw | 2026.3.31 |
| CVE-2026-41333 | 04/23/2026 | 3.7 | Low | Other | 2026.3.31 |
| CVE-2026-41354 | 04/23/2026 | 3.7 | Low | Path traversal | 2026.4.2 |
| CVE-2026-41357 | 04/23/2026 | 3.3 | Low | Other | 2026.3.31 |
| CVE-2026-41329 | 04/21/2026 | 9.9 | Critical | Authorisation flaw | 2026.3.31 |
| CVE-2026-41303 | 04/21/2026 | 8.8 | High | Authorisation flaw | 2026.3.28 |
| CVE-2026-41294 | 04/21/2026 | 8.6 | High | Other | 2026.3.28 |
| CVE-2026-41296 | 04/21/2026 | 8.2 | High | Race condition | 2026.3.31 |
| CVE-2026-41295 | 04/21/2026 | 7.8 | High | Command execution or injection | 2026.4.2 |
| CVE-2026-41297 | 04/21/2026 | 7.6 | High | Server-side request forgery | 2026.3.31 |
| CVE-2026-41302 | 04/21/2026 | 7.6 | High | Server-side request forgery | 2026.3.31 |
| CVE-2026-41299 | 04/21/2026 | 7.1 | High | Command execution or injection | 2026.3.28 |
| CVE-2026-41300 | 04/21/2026 | 6.5 | Medium | Other | 2026.3.31 |
| CVE-2026-40045 | 04/21/2026 | 5.7 | Medium | Other | 2026.4.2 |
| CVE-2026-41298 | 04/21/2026 | 5.4 | Medium | Authorisation flaw | 2026.4.2 |
| CVE-2026-41301 | 04/21/2026 | 5.3 | Medium | Other | 2026.3.31 |
| CVE-2026-41331 | 04/21/2026 | 5.3 | Medium | Other | 2026.3.31 |
| CVE-2026-41330 | 04/21/2026 | 4.4 | Medium | Other | 2026.3.31 |
| CVE-2026-41389 | 04/20/2026 | 5.8 | Medium | Path traversal | 2026.4.15 |
| CVE-2026-3690 | 04/11/2026 | 7.4 | High | Other | Not stated |
| CVE-2026-3689 | 04/11/2026 | 6.5 | Medium | Path traversal | Not stated |
| CVE-2026-3691 | 04/11/2026 | 5.3 | Medium | Information exposure | Not stated |
| CVE-2026-35643 | 04/10/2026 | 8.8 | High | Other | 2026.3.22 |
| CVE-2026-35663 | 04/10/2026 | 8.8 | High | Authorisation flaw | 2026.3.25 |
| CVE-2026-35666 | 04/10/2026 | 8.8 | High | Path traversal | 2026.3.22 |
| CVE-2026-35669 | 04/10/2026 | 8.8 | High | Authorisation flaw | 2026.3.25 |
| CVE-2026-35653 | 04/10/2026 | 8.1 | High | Authorisation flaw | 2026.3.24 |
| CVE-2026-35660 | 04/10/2026 | 8.1 | High | Authorisation flaw | 2026.3.23 |
| CVE-2026-35641 | 04/10/2026 | 7.8 | High | Other | 2026.3.24 |
| CVE-2026-35668 | 04/10/2026 | 7.7 | High | Path traversal | 2026.3.24 |
| CVE-2026-35650 | 04/10/2026 | 7.5 | High | Other | 2026.3.22 |
| CVE-2026-35621 | 04/10/2026 | 6.5 | Medium | Authorisation flaw | 2026.3.24 |
| CVE-2026-35649 | 04/10/2026 | 6.5 | Medium | Other | 2026.3.22 |
| CVE-2026-35652 | 04/10/2026 | 6.5 | Medium | Other | 2026.3.22 |
| CVE-2026-35656 | 04/10/2026 | 6.5 | Medium | Authentication flaw | 2026.3.22 |
| CVE-2026-35657 | 04/10/2026 | 6.5 | Medium | Authorisation flaw | 2026.3.25 |
| CVE-2026-35658 | 04/10/2026 | 6.5 | Medium | Authorisation flaw | 2026.3.2 |
| CVE-2026-35667 | 04/10/2026 | 6.1 | Medium | Other | 2026.3.24 |
| CVE-2026-35670 | 04/10/2026 | 5.9 | Medium | Command execution or injection | 2026.3.22 |
| CVE-2026-35655 | 04/10/2026 | 5.7 | Medium | Command execution or injection | 2026.3.22 |
| CVE-2026-6011 | 04/10/2026 | 5.6 | Medium | Server-side request forgery | Not stated |
| CVE-2026-35620 | 04/10/2026 | 5.4 | Medium | Authorisation flaw | 2026.3.24 |
| CVE-2026-35647 | 04/10/2026 | 5.3 | Medium | Authentication flaw | 2026.3.25 |
| CVE-2026-35654 | 04/10/2026 | 5.3 | Medium | Authentication flaw | 2026.3.25 |
| CVE-2026-35661 | 04/10/2026 | 5.3 | Medium | Authentication flaw | 2026.3.25 |
| CVE-2026-35664 | 04/10/2026 | 5.3 | Medium | Authentication flaw | 2026.3.25 |
| CVE-2026-35665 | 04/10/2026 | 5.3 | Medium | Other | 2026.3.24 |
| CVE-2026-35659 | 04/10/2026 | 4.6 | Medium | Authentication flaw | 2026.3.22 |
| CVE-2026-35619 | 04/10/2026 | 4.3 | Medium | Authorisation flaw | 2026.3.24 |
| CVE-2026-35651 | 04/10/2026 | 4.3 | Medium | Other | Not stated |
| CVE-2026-35662 | 04/10/2026 | 4.3 | Medium | Authorisation flaw | 2026.3.22 |
| CVE-2026-35648 | 04/10/2026 | 3.7 | Low | Race condition | 2026.3.22 |
| CVE-2026-35638 | 04/09/2026 | 8.8 | High | Other | 2026.3.22 |
| CVE-2026-35639 | 04/09/2026 | 8.8 | High | Authorisation flaw | 2026.3.22 |
| CVE-2026-34512 | 04/09/2026 | 8.1 | High | Authorisation flaw | 2026.3.25 |
| CVE-2026-35645 | 04/09/2026 | 8.1 | High | Authorisation flaw | 2026.3.25 |
| CVE-2026-35625 | 04/09/2026 | 7.8 | High | Authorisation flaw | 2026.3.25 |
| CVE-2026-35629 | 04/09/2026 | 7.4 | High | Server-side request forgery | 2026.3.25 |
| CVE-2026-35637 | 04/09/2026 | 7.3 | High | Other | 2026.3.22 |
| CVE-2026-35632 | 04/09/2026 | 7.1 | High | Other | Not stated |
| CVE-2026-35618 | 04/09/2026 | 6.5 | Medium | Other | 2026.3.23 |
| CVE-2026-35627 | 04/09/2026 | 6.5 | Medium | Other | 2026.3.22 |
| CVE-2026-35631 | 04/09/2026 | 6.5 | Medium | Authorisation flaw | 2026.3.22 |
| CVE-2026-35636 | 04/09/2026 | 6.5 | Medium | Other | Not stated |
| CVE-2026-35644 | 04/09/2026 | 6.5 | Medium | Information exposure | 2026.3.22 |
| CVE-2026-35622 | 04/09/2026 | 5.9 | Medium | Authentication flaw | 2026.3.22 |
| CVE-2026-35626 | 04/09/2026 | 5.3 | Medium | Other | 2026.3.22 |
| CVE-2026-35633 | 04/09/2026 | 5.3 | Medium | Resource exhaustion | 2026.3.22 |
| CVE-2026-35640 | 04/09/2026 | 5.3 | Medium | Other | 2026.3.25 |
| CVE-2026-35634 | 04/09/2026 | 5.1 | Medium | Authentication flaw | 2026.3.23 |
| CVE-2026-35623 | 04/09/2026 | 4.8 | Medium | Authentication flaw | 2026.3.25 |
| CVE-2026-35628 | 04/09/2026 | 4.8 | Medium | Authentication flaw | 2026.3.25 |
| CVE-2026-35635 | 04/09/2026 | 4.8 | Medium | Path traversal | 2026.3.22 |
| CVE-2026-35646 | 04/09/2026 | 4.8 | Medium | Authentication flaw | 2026.3.25 |
| CVE-2026-35642 | 04/09/2026 | 4.3 | Medium | Authentication flaw | 2026.3.25 |
| CVE-2026-35617 | 04/09/2026 | 4.2 | Medium | Command execution or injection | 2026.3.25 |
| CVE-2026-35624 | 04/09/2026 | 4.2 | Medium | Command execution or injection | 2026.3.22 |
| CVE-2026-40037 | 04/08/2026 | 6.5 | Medium | Other | 2026.3.31 |
| CVE-2026-34511 | 04/03/2026 | 5.3 | Medium | Other | 2026.4.2 |
| CVE-2026-34426 | 04/02/2026 | 7.6 | High | Command execution or injection | Not stated |
| CVE-2026-34425 | 04/02/2026 | 5.4 | Medium | Command execution or injection | Not stated |
| CVE-2026-34510 | 04/01/2026 | 5.3 | Medium | Other | 2026.3.22 |
| CVE-2026-33579 | 03/31/2026 | 9.9 | Critical | Authorisation flaw | 2026.3.28 |
| CVE-2026-32917 | 03/31/2026 | 9.8 | Critical | Command execution or injection | 2026.3.13 |
| CVE-2026-32916 | 03/31/2026 | 9.4 | Critical | Authorisation flaw | 2026.3.11 |
| CVE-2026-32920 | 03/31/2026 | 8.4 | High | Command execution or injection | 2026.3.12 |
| CVE-2026-34504 | 03/31/2026 | 8.3 | High | Server-side request forgery | 2026.3.28 |
| CVE-2026-33577 | 03/31/2026 | 8.1 | High | Authorisation flaw | 2026.3.28 |
| CVE-2026-34503 | 03/31/2026 | 8.1 | High | Authentication flaw | 2026.3.28 |
| CVE-2026-32982 | 03/31/2026 | 7.5 | High | Information exposure | 2026.3.13 |
| CVE-2026-32988 | 03/31/2026 | 7.5 | High | Race condition | 2026.3.11 |
| CVE-2026-32971 | 03/31/2026 | 7.1 | High | Other | 2026.3.11 |
| CVE-2026-32976 | 03/31/2026 | 6.5 | Medium | Authorisation flaw | 2026.3.11 |
| CVE-2026-34505 | 03/31/2026 | 6.5 | Medium | Authentication flaw | 2026.3.12 |
| CVE-2026-33576 | 03/31/2026 | 6.5 | Medium | Authorisation flaw | 2026.3.28 |
| CVE-2026-33580 | 03/31/2026 | 6.5 | Medium | Authentication flaw | 2026.3.28 |
| CVE-2026-33581 | 03/31/2026 | 6.5 | Medium | Path traversal | 2026.3.24 |
| CVE-2026-32921 | 03/31/2026 | 6.3 | Medium | Race condition | 2026.3.8 |
| CVE-2026-32977 | 03/31/2026 | 6.3 | Medium | Race condition | 2026.3.11 |
| CVE-2026-34506 | 03/31/2026 | 4.3 | Medium | Authorisation flaw | 2026.3.8 |
| CVE-2026-33578 | 03/31/2026 | 4.3 | Medium | Authorisation flaw | 2026.3.28 |
| CVE-2026-32970 | 03/31/2026 | 2.5 | Low | Authentication flaw | 2026.3.11 |
| CVE-2026-32922 | 03/29/2026 | 9.9 | Critical | Authorisation flaw | 2026.3.11 |
| CVE-2026-32924 | 03/29/2026 | 9.8 | Critical | Authorisation flaw | 2026.3.12 |
| CVE-2026-32973 | 03/29/2026 | 9.8 | Critical | Other | 2026.3.11 |
| CVE-2026-32975 | 03/29/2026 | 9.8 | Critical | Command execution or injection | 2026.3.12 |
| CVE-2026-32987 | 03/29/2026 | 9.8 | Critical | Other | 2026.3.13 |
| CVE-2026-32914 | 03/29/2026 | 8.8 | High | Authorisation flaw | 2026.3.12 |
| CVE-2026-32915 | 03/29/2026 | 8.8 | High | Authorisation flaw | 2026.3.11 |
| CVE-2026-33573 | 03/29/2026 | 8.8 | High | Authorisation flaw | 2026.3.11 |
| CVE-2026-32974 | 03/29/2026 | 8.6 | High | Other | 2026.3.12 |
| CVE-2026-32918 | 03/29/2026 | 8.4 | High | Authorisation flaw | 2026.3.11 |
| CVE-2026-33572 | 03/29/2026 | 8.4 | High | Other | 2026.2.17 |
| CVE-2026-32978 | 03/29/2026 | 8 | High | Authorisation flaw | 2026.3.11 |
| CVE-2026-32980 | 03/29/2026 | 7.5 | High | Resource exhaustion | 2026.3.13 |
| CVE-2026-33575 | 03/29/2026 | 7.5 | High | Authentication flaw | 2026.3.12 |
| CVE-2026-32979 | 03/29/2026 | 7.3 | High | Race condition | 2026.3.11 |
| CVE-2026-32972 | 03/29/2026 | 7.1 | High | Authorisation flaw | 2026.3.11 |
| CVE-2026-33574 | 03/29/2026 | 6.2 | Medium | Race condition | 2026.3.8 |
| CVE-2026-32919 | 03/29/2026 | 6.1 | Medium | Authorisation flaw | 2026.3.11 |
| CVE-2026-32923 | 03/29/2026 | 5.4 | Medium | Authorisation flaw | 2026.3.11 |
| CVE-2026-32846 | 03/26/2026 | 7.5 | High | Path traversal | 2026.3.28 |
| CVE-2026-32913 | 03/23/2026 | 9.3 | Critical | Authentication flaw | 2026.3.7 |
| CVE-2026-27646 | 03/23/2026 | 6.1 | Medium | Authorisation flaw | 2026.3.7 |
| CVE-2026-27183 | 03/23/2026 | 5.3 | Medium | Authorisation flaw | 2026.3.7 |
| CVE-2026-32042 | 03/21/2026 | 8.8 | High | Authorisation flaw | 2026.2.25 |
| CVE-2026-32051 | 03/21/2026 | 8.8 | High | Authorisation flaw | 2026.3.1 |
| CVE-2026-32064 | 03/21/2026 | 7.7 | High | Authentication flaw | 2026.2.21 |
| CVE-2026-32055 | 03/21/2026 | 7.6 | High | Path traversal | 2026.2.26 |
| CVE-2026-32048 | 03/21/2026 | 7.5 | High | Authorisation flaw | 2026.3.1 |
| CVE-2026-32049 | 03/21/2026 | 7.5 | High | Resource exhaustion | 2026.2.22 |
| CVE-2026-32056 | 03/21/2026 | 7.5 | High | Command execution or injection | 2026.2.22 |
| CVE-2026-32057 | 03/21/2026 | 7.1 | High | Command execution or injection | 2026.2.25 |
| CVE-2026-32043 | 03/21/2026 | 6.5 | Medium | Race condition | 2026.2.25 |
| CVE-2026-32053 | 03/21/2026 | 6.5 | Medium | Other | 2026.2.23 |
| CVE-2026-32054 | 03/21/2026 | 6.5 | Medium | Path traversal | 2026.2.25 |
| CVE-2026-32052 | 03/21/2026 | 6.4 | Medium | Command execution or injection | 2026.2.24 |
| CVE-2026-32045 | 03/21/2026 | 5.9 | Medium | Authentication flaw | 2026.2.21 |
| CVE-2026-32044 | 03/21/2026 | 5.5 | Medium | Resource exhaustion | 2026.3.2 |
| CVE-2026-32895 | 03/21/2026 | 5.4 | Medium | Authorisation flaw | 2026.2.26 |
| CVE-2026-32898 | 03/21/2026 | 5.4 | Medium | Command execution or injection | 2026.2.23 |
| CVE-2026-32046 | 03/21/2026 | 5.3 | Medium | Other | 2026.2.21 |
| CVE-2026-32065 | 03/21/2026 | 4.8 | Medium | Other | 2026.2.25 |
| CVE-2026-32896 | 03/21/2026 | 4.8 | Medium | Authentication flaw | 2026.2.21 |
| CVE-2026-32899 | 03/21/2026 | 4.3 | Medium | Authorisation flaw | 2026.2.25 |
| CVE-2026-32050 | 03/21/2026 | 3.7 | Low | Authorisation flaw | 2026.2.25 |
| CVE-2026-32067 | 03/21/2026 | 3.7 | Low | Authorisation flaw | 2026.2.26 |
| CVE-2026-32897 | 03/21/2026 | 3.7 | Low | Other | 2026.2.22 |
| CVE-2026-32058 | 03/21/2026 | 2.6 | Low | Authorisation flaw | 2026.2.26 |
| CVE-2026-22172 | 03/20/2026 | 9.9 | Critical | Authorisation flaw | 2026.3.12 |
| CVE-2026-32038 | 03/19/2026 | 9.8 | Critical | Authorisation flaw | 2026.2.24 |
| CVE-2026-32013 | 03/19/2026 | 8.8 | High | Path traversal | 2026.2.25 |
| CVE-2026-31998 | 03/19/2026 | 8.6 | High | Authorisation flaw | Not stated |
| CVE-2026-32034 | 03/19/2026 | 8.1 | High | Command execution or injection | 2026.2.21 |
| CVE-2026-32014 | 03/19/2026 | 8 | High | Authentication flaw | 2026.2.26 |
| CVE-2026-32015 | 03/19/2026 | 7.8 | High | Command execution or injection | 2026.2.19 |
| CVE-2026-32016 | 03/19/2026 | 7.8 | High | Command execution or injection | 2026.2.22 |
| CVE-2026-32032 | 03/19/2026 | 7.8 | High | Command execution or injection | 2026.2.22 |
| CVE-2026-28461 | 03/19/2026 | 7.5 | High | Resource exhaustion | 2026.3.1 |
| CVE-2026-32011 | 03/19/2026 | 7.5 | High | Resource exhaustion | 2026.3.2 |
| CVE-2026-32025 | 03/19/2026 | 7.5 | High | Authentication flaw | 2026.2.25 |
| CVE-2026-32030 | 03/19/2026 | 7.5 | High | Path traversal | 2026.2.19 |
| CVE-2026-31989 | 03/19/2026 | 7.4 | High | Server-side request forgery | 2026.3.1 |
| CVE-2026-32019 | 03/19/2026 | 7.4 | High | Server-side request forgery | 2026.2.22 |
| CVE-2026-27566 | 03/19/2026 | 7.1 | High | Command execution or injection | 2026.2.22 |
| CVE-2026-28460 | 03/19/2026 | 7.1 | High | Command execution or injection | 2026.2.22 |
| CVE-2026-31992 | 03/19/2026 | 7.1 | High | Command execution or injection | 2026.2.23 |
| CVE-2026-31994 | 03/19/2026 | 7.1 | High | Command execution or injection | 2026.2.19 |
| CVE-2026-32000 | 03/19/2026 | 7.1 | High | Command execution or injection | 2026.2.19 |
| CVE-2026-32017 | 03/19/2026 | 7.1 | High | Command execution or injection | 2026.2.19 |
| CVE-2026-32023 | 03/19/2026 | 7.1 | High | Authorisation flaw | 2026.2.24 |
| CVE-2026-32041 | 03/19/2026 | 6.9 | Medium | Authentication flaw | 2026.3.1 |
| CVE-2026-29607 | 03/19/2026 | 6.8 | Medium | Command execution or injection | 2026.2.22 |
| CVE-2026-32005 | 03/19/2026 | 6.8 | Medium | Authorisation flaw | 2026.2.25 |
| CVE-2026-32007 | 03/19/2026 | 6.8 | Medium | Path traversal | 2026.2.23 |
| CVE-2026-29608 | 03/19/2026 | 6.7 | Medium | Command execution or injection | Not stated |
| CVE-2026-32003 | 03/19/2026 | 6.6 | Medium | Command execution or injection | 2026.2.22 |
| CVE-2026-28449 | 03/19/2026 | 6.5 | Medium | Other | 2026.2.25 |
| CVE-2026-32004 | 03/19/2026 | 6.5 | Medium | Authentication flaw | 2026.3.2 |
| CVE-2026-32008 | 03/19/2026 | 6.5 | Medium | Other | 2026.2.21 |
| CVE-2026-32021 | 03/19/2026 | 6.5 | Medium | Authorisation flaw | 2026.2.22 |
| CVE-2026-32022 | 03/19/2026 | 6.5 | Medium | Command execution or injection | 2026.2.21 |
| CVE-2026-32026 | 03/19/2026 | 6.5 | Medium | Path traversal | 2026.2.24 |
| CVE-2026-32027 | 03/19/2026 | 6.5 | Medium | Authorisation flaw | 2026.2.26 |
| CVE-2026-32033 | 03/19/2026 | 6.5 | Medium | Path traversal | 2026.2.24 |
| CVE-2026-32036 | 03/19/2026 | 6.5 | Medium | Path traversal | 2026.2.26 |
| CVE-2026-31999 | 03/19/2026 | 6.3 | Medium | Command execution or injection | 2026.3.1 |
| CVE-2026-32010 | 03/19/2026 | 6.3 | Medium | Command execution or injection | 2026.2.22 |
| CVE-2026-22176 | 03/19/2026 | 6.1 | Medium | Command execution or injection | 2026.2.19 |
| CVE-2026-31990 | 03/19/2026 | 6.1 | Medium | Path traversal | 2026.3.2 |
| CVE-2026-31997 | 03/19/2026 | 6 | Medium | Race condition | 2026.3.1 |
| CVE-2026-32037 | 03/19/2026 | 6 | Medium | Server-side request forgery | 2026.2.22 |
| CVE-2026-32035 | 03/19/2026 | 5.9 | Medium | Authorisation flaw | 2026.3.2 |
| CVE-2026-32039 | 03/19/2026 | 5.9 | Medium | Authorisation flaw | 2026.2.22 |
| CVE-2026-32009 | 03/19/2026 | 5.7 | Medium | Command execution or injection | 2026.2.24 |
| CVE-2026-32024 | 03/19/2026 | 5.5 | Medium | Path traversal | 2026.2.22 |
| CVE-2026-32001 | 03/19/2026 | 5.4 | Medium | Authorisation flaw | 2026.2.22 |
| CVE-2026-27670 | 03/19/2026 | 5.3 | Medium | Race condition | 2026.3.2 |
| CVE-2026-31995 | 03/19/2026 | 5.3 | Medium | Command execution or injection | 2026.2.19 |
| CVE-2026-32002 | 03/19/2026 | 5.3 | Medium | Information exposure | 2026.2.23 |
| CVE-2026-32028 | 03/19/2026 | 5.3 | Medium | Authorisation flaw | 2026.2.25 |
| CVE-2026-32029 | 03/19/2026 | 5.3 | Medium | Authentication flaw | 2026.2.21 |
| CVE-2026-31993 | 03/19/2026 | 4.8 | Medium | Command execution or injection | 2026.2.22 |
| CVE-2026-32031 | 03/19/2026 | 4.8 | Medium | Authentication flaw | 2026.2.26 |
| CVE-2026-32040 | 03/19/2026 | 4.6 | Medium | Command execution or injection | 2026.2.23 |
| CVE-2026-31996 | 03/19/2026 | 4.4 | Medium | Command execution or injection | 2026.2.19 |
| CVE-2026-31991 | 03/19/2026 | 3.7 | Low | Authorisation flaw | 2026.2.26 |
| CVE-2026-32018 | 03/19/2026 | 3.6 | Low | Race condition | 2026.2.19 |
| CVE-2026-32020 | 03/19/2026 | 3.3 | Low | Path traversal | 2026.2.22 |
| CVE-2026-32006 | 03/19/2026 | 3.1 | Low | Authorisation flaw | 2026.2.26 |
| CVE-2026-22171 | 03/18/2026 | 8.2 | High | Path traversal | 2026.2.19 |
| CVE-2026-22181 | 03/18/2026 | 7.6 | High | Server-side request forgery | 2026.3.2 |
| CVE-2026-22179 | 03/18/2026 | 7.2 | High | Command execution or injection | 2026.2.22 |
| CVE-2026-22175 | 03/18/2026 | 7.1 | High | Command execution or injection | 2026.2.23 |
| CVE-2026-22174 | 03/18/2026 | 6.8 | Medium | Authentication flaw | 2026.2.22 |
| CVE-2026-22169 | 03/18/2026 | 6.7 | Medium | Command execution or injection | 2026.2.22 |
| CVE-2026-22168 | 03/18/2026 | 6.5 | Medium | Command execution or injection | 2026.2.21 |
| CVE-2026-22170 | 03/18/2026 | 6.5 | Medium | Authorisation flaw | 2026.2.22 |
| CVE-2026-22178 | 03/18/2026 | 6.5 | Medium | Resource exhaustion | 2026.2.19 |
| CVE-2026-27522 | 03/18/2026 | 6.5 | Medium | Path traversal | 2026.2.24 |
| CVE-2026-22177 | 03/18/2026 | 6.1 | Medium | Other | 2026.2.21 |
| CVE-2026-22217 | 03/18/2026 | 6.1 | Medium | Command execution or injection | 2026.2.23 |
| CVE-2026-27523 | 03/18/2026 | 6.1 | Medium | Path traversal | 2026.2.24 |
| CVE-2026-27545 | 03/18/2026 | 6.1 | Medium | Race condition | 2026.2.26 |
| CVE-2026-22180 | 03/18/2026 | 5.3 | Medium | Path traversal | 2026.3.2 |
| CVE-2026-27524 | 03/18/2026 | 4.3 | Medium | Other | 2026.2.21 |
| CVE-2026-32302 | 03/13/2026 | 8.1 | High | Authentication flaw | 2026.3.11 |
| CVE-2026-4039 | 03/12/2026 | 6.3 | Medium | Command execution or injection | Not stated |
| CVE-2026-4040 | 03/12/2026 | 3.3 | Low | Information exposure | Not stated |
| CVE-2026-30741 | 03/11/2026 | 9.8 | Critical | Command execution or injection | Not stated |
| CVE-2026-32059 | 03/11/2026 | 8.8 | High | Authorisation flaw | 2026.2.23 |
| CVE-2026-32060 | 03/11/2026 | 8.8 | High | Path traversal | 2026.2.14 |
| CVE-2026-32062 | 03/11/2026 | 7.5 | High | Resource exhaustion | 2026.2.22 |
| CVE-2026-32063 | 03/11/2026 | 7.1 | High | Command execution or injection | 2026.2.21 |
| CVE-2026-32061 | 03/11/2026 | 4.4 | Medium | Path traversal | 2026.2.17 |
| CVE-2026-28466 | 03/05/2026 | 9.9 | Critical | Authorisation flaw | 2026.2.14 |
| CVE-2026-28391 | 03/05/2026 | 9.8 | Critical | Command execution or injection | 2026.2.2 |
| CVE-2026-28470 | 03/05/2026 | 9.8 | Critical | Command execution or injection | 2026.2.2 |
| CVE-2026-28474 | 03/05/2026 | 9.8 | Critical | Authorisation flaw | 2026.2.6 |
| CVE-2026-28446 | 03/05/2026 | 9.4 | Critical | Other | 2026.2.1 |
| CVE-2026-29610 | 03/05/2026 | 8.8 | High | Other | 2026.2.14 |
| CVE-2026-28463 | 03/05/2026 | 8.4 | High | Command execution or injection | 2026.2.14 |
| CVE-2026-28485 | 03/05/2026 | 8.4 | High | Authentication flaw | 2026.2.12 |
| CVE-2026-28451 | 03/05/2026 | 8.3 | High | Server-side request forgery | 2026.2.14 |
| CVE-2026-28476 | 03/05/2026 | 8.3 | High | Server-side request forgery | 2026.2.14 |
| CVE-2026-28447 | 03/05/2026 | 8.1 | High | Path traversal | 2026.2.1 |
| CVE-2026-28458 | 03/05/2026 | 8.1 | High | Authentication flaw | 2026.2.1 |
| CVE-2026-28472 | 03/05/2026 | 8.1 | High | Authentication flaw | 2026.2.2 |
| CVE-2026-28473 | 03/05/2026 | 8.1 | High | Authorisation flaw | 2026.2.2 |
| CVE-2026-28393 | 03/05/2026 | 7.7 | High | Path traversal | 2026.2.14 |
| CVE-2026-28468 | 03/05/2026 | 7.7 | High | Authentication flaw | 2026.2.14 |
| CVE-2026-28392 | 03/05/2026 | 7.5 | High | Authorisation flaw | 2026.2.14 |
| CVE-2026-28453 | 03/05/2026 | 7.5 | High | Path traversal | 2026.2.14 |
| CVE-2026-28454 | 03/05/2026 | 7.5 | High | Authentication flaw | 2026.2.2 |
| CVE-2026-28462 | 03/05/2026 | 7.5 | High | Path traversal | 2026.2.13 |
| CVE-2026-28469 | 03/05/2026 | 7.5 | High | Authorisation flaw | 2026.2.14 |
| CVE-2026-28478 | 03/05/2026 | 7.5 | High | Resource exhaustion | 2026.2.13 |
| CVE-2026-28479 | 03/05/2026 | 7.5 | High | Other | 2026.2.15 |
| CVE-2026-29609 | 03/05/2026 | 7.5 | High | Resource exhaustion | 2026.2.14 |
| CVE-2026-29611 | 03/05/2026 | 7.5 | High | Path traversal | 2026.2.14 |
| CVE-2026-28448 | 03/05/2026 | 7.3 | High | Authorisation flaw | 2026.2.1 |
| CVE-2026-28456 | 03/05/2026 | 7.2 | High | Other | 2026.2.14 |
| CVE-2026-28459 | 03/05/2026 | 7.1 | High | Path traversal | 2026.2.12 |
| CVE-2026-28477 | 03/05/2026 | 7.1 | High | Other | 2026.2.14 |
| CVE-2026-28482 | 03/05/2026 | 7.1 | High | Path traversal | 2026.2.12 |
| CVE-2026-28450 | 03/05/2026 | 6.8 | Medium | Authentication flaw | 2026.2.12 |
| CVE-2026-28394 | 03/05/2026 | 6.5 | Medium | Resource exhaustion | 2026.2.15 |
| CVE-2026-28395 | 03/05/2026 | 6.5 | Medium | Other | 2026.2.12 |
| CVE-2026-28467 | 03/05/2026 | 6.5 | Medium | Server-side request forgery | 2026.2.2 |
| CVE-2026-28480 | 03/05/2026 | 6.5 | Medium | Authentication flaw | 2026.2.14 |
| CVE-2026-28481 | 03/05/2026 | 6.5 | Medium | Other | Not stated |
| CVE-2026-29606 | 03/05/2026 | 6.5 | Medium | Authentication flaw | 2026.2.14 |
| CVE-2026-28457 | 03/05/2026 | 6.1 | Medium | Path traversal | 2026.2.14 |
| CVE-2026-28486 | 03/05/2026 | 6.1 | Medium | Path traversal | 2026.2.14 |
| CVE-2026-28464 | 03/05/2026 | 5.9 | Medium | Other | 2026.2.12 |
| CVE-2026-28465 | 03/05/2026 | 5.9 | Medium | Authentication flaw | 2026.2.3 |
| CVE-2026-29613 | 03/05/2026 | 5.9 | Medium | Authentication flaw | 2026.2.12 |
| CVE-2026-28452 | 03/05/2026 | 5.5 | Medium | Resource exhaustion | 2026.2.14 |
| CVE-2026-29612 | 03/05/2026 | 5.5 | Medium | Resource exhaustion | 2026.2.14 |
| CVE-2026-28471 | 03/05/2026 | 5.3 | Medium | Authentication flaw | 2026.2.2 |
| CVE-2026-28475 | 03/05/2026 | 4.8 | Medium | Other | 2026.2.13 |
| CVE-2026-28363 | 02/27/2026 | 9.9 | Critical | Command execution or injection | 2026.2.23 |
| CVE-2026-27487 | 02/21/2026 | 7.6 | High | Command execution or injection | Not stated |
| CVE-2026-27488 | 02/21/2026 | 7.3 | High | Server-side request forgery | Not stated |
| CVE-2026-27486 | 02/21/2026 | 5.3 | Medium | Other | Not stated |
| CVE-2026-27485 | 02/21/2026 | 4.4 | Medium | Other | Not stated |
| CVE-2026-27484 | 02/21/2026 | 4.3 | Medium | Authorisation flaw | Not stated |
| CVE-2026-27576 | 02/21/2026 | 4 | Medium | Resource exhaustion | Not stated |
| CVE-2026-27002 | 02/20/2026 | 9.8 | Critical | Other | 2026.2.15 |
| CVE-2026-27001 | 02/20/2026 | 7.8 | High | Command execution or injection | 2026.2.15 |
| CVE-2026-26972 | 02/20/2026 | 6.7 | Medium | Path traversal | Not stated |
| CVE-2026-27008 | 02/20/2026 | 6.7 | Medium | Path traversal | 2026.2.15 |
| CVE-2026-26328 | 02/20/2026 | 6.5 | Medium | Authorisation flaw | 2026.2.14 |
| CVE-2026-26329 | 02/20/2026 | 6.5 | Medium | Path traversal | 2026.2.14 |
| CVE-2026-27009 | 02/20/2026 | 5.8 | Medium | Command execution or injection | 2026.2.15 |
| CVE-2026-27003 | 02/20/2026 | 5.5 | Medium | Authentication flaw | 2026.2.15 |
| CVE-2026-27004 | 02/20/2026 | 5.5 | Medium | Information exposure | 2026.2.15 |
| CVE-2026-27007 | 02/20/2026 | 3.3 | Low | Other | 2026.2.15 |
| CVE-2026-26323 | 02/19/2026 | 8.8 | High | Command execution or injection | Not stated |
| CVE-2026-26322 | 02/19/2026 | 7.6 | High | Server-side request forgery | Not stated |
| CVE-2026-25474 | 02/19/2026 | 7.5 | High | Authentication flaw | Not stated |
| CVE-2026-26316 | 02/19/2026 | 7.5 | High | Authorisation flaw | 2026.2.13 |
| CVE-2026-26319 | 02/19/2026 | 7.5 | High | Authentication flaw | Not stated |
| CVE-2026-26321 | 02/19/2026 | 7.5 | High | Path traversal | Not stated |
| CVE-2026-26324 | 02/19/2026 | 7.5 | High | Server-side request forgery | 2026.2.14 |
| CVE-2026-26325 | 02/19/2026 | 7.2 | High | Authorisation flaw | 2026.2.14 |
| CVE-2026-26317 | 02/19/2026 | 7.1 | High | Other | 2026.2.14 |
| CVE-2026-26320 | 02/19/2026 | 6.5 | Medium | Other | Not stated |
| CVE-2026-26327 | 02/19/2026 | 6.5 | Medium | Authentication flaw | 2026.2.14 |
| CVE-2026-26326 | 02/19/2026 | 4.3 | Medium | Information exposure | 2026.2.14 |
| CVE-2026-24764 | 02/19/2026 | 3.7 | Low | Command execution or injection | Not stated |
| CVE-2026-25593 | 02/06/2026 | 8.4 | High | Command execution or injection | 2026.1.20 |
| CVE-2026-25157 | 02/04/2026 | 7.7 | High | Command execution or injection | 2026.1.29 |
| CVE-2026-25475 | 02/04/2026 | 6.5 | Medium | Path traversal | 2026.1.30 |
| CVE-2026-24763 | 02/02/2026 | 8.8 | High | Command execution or injection | 2026.1.29 |
| CVE-2026-25253 | 02/01/2026 | 8.8 | High | Other | 2026.1.29 |
Advisories that are not CVEs
- ClawHavoc
- A campaign of malicious skills on ClawHub. Antiy CERT counted at least 1184; Koi Security flagged 341 of 2857 audited skills (February 2026). Antiy CERT, Koi Security (via The Hacker News)
How this list is built
We query the NVD for every CVE whose description names OpenClaw or its former names, Clawdbot and Moltbot, and leave out rejected entries. The fixed version comes from the NVD description. We refresh the data and publish the change in the changelog.