VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293841 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-26819 | redhat_vex | cJSON: cJSON rejects a valid text | known affected: 13 | 2026-07-01T06:10:33+00:00 | Vulnerability · Source |
| CVE-2023-53154 | redhat_vex | cjson: Heap based buffer overflow at cJSON_ParseWithLength function | known affected: 3 | 2026-07-01T06:10:31+00:00 | Vulnerability · Source |
| CVE-2026-54270 | redhat_vex | protobufjs: protobufjs: Denial of Service due to excessive memory consumption | known affected: 12 known not affected: 33 | 2026-07-01T05:08:48+00:00 | Vulnerability · Source |
| CVE-2026-54269 | redhat_vex | protobufjs: protobufjs-cli: protobufjs: Denial of Service due to name collision with runtime helpers | known affected: 12 known not affected: 33 | 2026-07-01T05:08:48+00:00 | Vulnerability · Source |
| CVE-2026-40989 | redhat_vex | spring-cloud-function-context: Spring Cloud Function: Denial of Service via infinite recursion in routing layer | known affected: 1 | 2026-07-01T04:38:32+00:00 | Vulnerability · Source |
| CVE-2017-5603 | suse_vex | SUSE CVE CVE-2017-5603 | recommended: 6 | 2026-07-01T04:10:16+00:00 | Vulnerability · Source |
| CVE-2017-11124 | suse_vex | SUSE CVE CVE-2017-11124 | recommended: 6 | 2026-07-01T04:10:01+00:00 | Vulnerability · Source |
| CVE-2017-11125 | suse_vex | SUSE CVE CVE-2017-11125 | recommended: 6 | 2026-07-01T04:10:00+00:00 | Vulnerability · Source |
| CVE-2018-18504 | suse_vex | SUSE CVE CVE-2018-18504 | known not affected: 154 recommended: 9 | 2026-07-01T04:09:20+00:00 | Vulnerability · Source |
| CVE-2019-13173 | suse_vex | SUSE CVE CVE-2019-13173 | known affected: 82 known not affected: 96 recommended: 468 | 2026-07-01T04:08:53+00:00 | Vulnerability · Source |
| CVE-2020-7068 | suse_vex | SUSE CVE CVE-2020-7068 | known not affected: 543 recommended: 5537 | 2026-07-01T04:08:28+00:00 | Vulnerability · Source |
| CVE-2020-26972 | suse_vex | SUSE CVE CVE-2020-26972 | recommended: 9 | 2026-07-01T04:07:49+00:00 | Vulnerability · Source |
| CVE-2020-35518 | suse_vex | SUSE CVE CVE-2020-35518 | known not affected: 60 recommended: 47 | 2026-07-01T04:07:37+00:00 | Vulnerability · Source |
| CVE-2021-28879 | suse_vex | SUSE CVE CVE-2021-28879 | known not affected: 374 recommended: 14 | 2026-07-01T04:07:06+00:00 | Vulnerability · Source |
| CVE-2022-45407 | suse_vex | SUSE CVE CVE-2022-45407 | known affected: 1 recommended: 9 | 2026-07-01T04:04:28+00:00 | Vulnerability · Source |
| CVE-2022-45419 | suse_vex | SUSE CVE CVE-2022-45419 | known affected: 1 recommended: 9 | 2026-07-01T04:04:27+00:00 | Vulnerability · Source |
| CVE-2023-0645 | suse_vex | SUSE CVE CVE-2023-0645 | No product status | 2026-07-01T04:02:19+00:00 | Vulnerability · Source |
| CVE-2023-4234 | suse_vex | SUSE CVE CVE-2023-4234 | recommended: 6 | 2026-07-01T04:01:50+00:00 | Vulnerability · Source |
| CVE-2023-4235 | suse_vex | SUSE CVE CVE-2023-4235 | recommended: 3 | 2026-07-01T04:01:48+00:00 | Vulnerability · Source |
| CVE-2023-6683 | suse_vex | SUSE CVE CVE-2023-6683 | known affected: 389 known not affected: 1708 recommended: 789 | 2026-07-01T04:01:30+00:00 | Vulnerability · Source |
| CVE-2023-30586 | suse_vex | SUSE CVE CVE-2023-30586 | known not affected: 562 recommended: 5 | 2026-07-01T04:01:02+00:00 | Vulnerability · Source |
| CVE-2023-49295 | suse_vex | SUSE CVE CVE-2023-49295 | recommended: 10 | 2026-07-01T04:00:23+00:00 | Vulnerability · Source |
| CVE-2024-0754 | suse_vex | SUSE CVE CVE-2024-0754 | known affected: 93 recommended: 9 | 2026-07-01T03:58:05+00:00 | Vulnerability · Source |
| CVE-2024-1557 | suse_vex | SUSE CVE CVE-2024-1557 | known affected: 42 recommended: 9 | 2026-07-01T03:58:01+00:00 | Vulnerability · Source |
| CVE-2024-4775 | suse_vex | SUSE CVE CVE-2024-4775 | known affected: 33 recommended: 9 | 2026-07-01T03:57:52+00:00 | Vulnerability · Source |
| CVE-2024-5290 | suse_vex | SUSE CVE CVE-2024-5290 | known not affected: 48 | 2026-07-01T03:57:51+00:00 | Vulnerability · Source |
| CVE-2024-7540 | suse_vex | SUSE CVE CVE-2024-7540 | recommended: 9 | 2026-07-01T03:57:44+00:00 | Vulnerability · Source |
| CVE-2024-7541 | suse_vex | SUSE CVE CVE-2024-7541 | recommended: 9 | 2026-07-01T03:57:43+00:00 | Vulnerability · Source |
| CVE-2024-7543 | suse_vex | SUSE CVE CVE-2024-7543 | recommended: 6 | 2026-07-01T03:57:41+00:00 | Vulnerability · Source |
| CVE-2024-7544 | suse_vex | SUSE CVE CVE-2024-7544 | recommended: 9 | 2026-07-01T03:57:40+00:00 | Vulnerability · Source |
| CVE-2024-7547 | suse_vex | SUSE CVE CVE-2024-7547 | recommended: 6 | 2026-07-01T03:57:39+00:00 | Vulnerability · Source |
| CVE-2024-22189 | suse_vex | SUSE CVE CVE-2024-22189 | recommended: 37 | 2026-07-01T03:57:11+00:00 | Vulnerability · Source |
| CVE-2024-24788 | suse_vex | SUSE CVE CVE-2024-24788 | known not affected: 57 recommended: 129 | 2026-07-01T03:57:05+00:00 | Vulnerability · Source |
| CVE-2024-31079 | suse_vex | SUSE CVE CVE-2024-31079 | known not affected: 60 | 2026-07-01T03:55:49+00:00 | Vulnerability · Source |
| CVE-2024-34158 | suse_vex | SUSE CVE CVE-2024-34158 | recommended: 538 | 2026-07-01T03:55:42+00:00 | Vulnerability · Source |
| CVE-2024-45157 | suse_vex | SUSE CVE CVE-2024-45157 | recommended: 14 | 2026-07-01T03:53:42+00:00 | Vulnerability · Source |
| CVE-2025-14009 | suse_vex | SUSE CVE CVE-2025-14009 | recommended: 6 | 2026-07-01T03:47:40+00:00 | Vulnerability · Source |
| CVE-2025-24965 | suse_vex | SUSE CVE CVE-2025-24965 | known affected: 390 recommended: 4 | 2026-07-01T03:45:48+00:00 | Vulnerability · Source |
| CVE-2025-47917 | suse_vex | SUSE CVE CVE-2025-47917 | recommended: 11 | 2026-07-01T03:42:03+00:00 | Vulnerability · Source |
| CVE-2025-48965 | suse_vex | SUSE CVE CVE-2025-48965 | recommended: 11 | 2026-07-01T03:41:58+00:00 | Vulnerability · Source |
| CVE-2025-49600 | suse_vex | SUSE CVE CVE-2025-49600 | recommended: 27 | 2026-07-01T03:41:52+00:00 | Vulnerability · Source |
| CVE-2025-52496 | suse_vex | SUSE CVE CVE-2025-52496 | recommended: 27 | 2026-07-01T03:41:47+00:00 | Vulnerability · Source |
| CVE-2025-62507 | suse_vex | SUSE CVE CVE-2025-62507 | known not affected: 62 recommended: 2 | 2026-07-01T03:41:17+00:00 | Vulnerability · Source |
| CVE-2025-68463 | suse_vex | SUSE CVE CVE-2025-68463 | recommended: 5 | 2026-07-01T03:40:39+00:00 | Vulnerability · Source |
| CVE-2025-68616 | suse_vex | SUSE CVE CVE-2025-68616 | recommended: 7 | 2026-07-01T03:40:37+00:00 | Vulnerability · Source |
| CVE-2026-0847 | suse_vex | SUSE CVE CVE-2026-0847 | recommended: 3 | 2026-07-01T03:40:04+00:00 | Vulnerability · Source |
| CVE-2026-1801 | suse_vex | SUSE CVE CVE-2026-1801 | known affected: 163 known not affected: 13 recommended: 81 | 2026-07-01T03:39:50+00:00 | Vulnerability · Source |
| CVE-2026-2047 | suse_vex | SUSE CVE CVE-2026-2047 | known not affected: 34 recommended: 2 | 2026-07-01T03:39:44+00:00 | Vulnerability · Source |
| CVE-2026-2492 | suse_vex | SUSE CVE CVE-2026-2492 | No product status | 2026-07-01T03:39:37+00:00 | Vulnerability · Source |
| CVE-2026-2921 | suse_vex | SUSE CVE CVE-2026-2921 | known affected: 809 recommended: 24 | 2026-07-01T03:39:26+00:00 | Vulnerability · Source |