VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
305424 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-83615 | redhat_vex | xmldom: @xmldom/xmldom: xmldom: Denial of Service via quadratic memory consumption | fixed: 1 known affected: 2 known not affected: 25 | 2026-10-05T03:28:07+00:00 | Vulnerability · Source |
| CVE-2026-83613 | redhat_vex | xmldom: @xmldom/xmldom: xmldom: Denial of Service due to quadratic-time attribute processing | fixed: 1 known affected: 3 known not affected: 24 | 2026-10-05T03:28:05+00:00 | Vulnerability · Source |
| CVE-2026-83609 | redhat_vex | @xmldom/xmldom: xmldom: Markup injection via embedded line terminators in XML names | known affected: 3 known not affected: 22 | 2026-10-05T03:28:00+00:00 | Vulnerability · Source |
| CVE-2026-76183 | redhat_vex | tomcat: Apache Tomcat: Authentication Bypass in WebSocket Endpoints | fixed: 42 known affected: 79 known not affected: 12 | 2026-10-05T03:27:47+00:00 | Vulnerability · Source |
| CVE-2026-76561 | redhat_vex | pki-core: Dogtag/PKI: certprofile-import allows code execution via unsanitized profile content (ExternalProcessConstraint) | fixed: 97 known affected: 58 | 2026-10-05T03:18:16+00:00 | Vulnerability · Source |
| CVE-2026-102317 | redhat_vex | chromium-browser: chromium-browser: Improper privilege management in Mojo | known not affected: 1 | 2026-10-05T00:58:07+00:00 | Vulnerability · Source |
| CVE-2017-7383 | suse_vex | SUSE CVE CVE-2017-7383 | known affected: 6 recommended: 28 | 2026-10-04T23:41:15+00:00 | Vulnerability · Source |
| CVE-2019-19227 | suse_vex | SUSE CVE CVE-2019-19227 | known affected: 117 known not affected: 61 recommended: 634 | 2026-10-04T23:40:38+00:00 | Vulnerability · Source |
| CVE-2020-36385 | suse_vex | SUSE CVE CVE-2020-36385 | known affected: 299 known not affected: 156 recommended: 1743 | 2026-10-04T23:40:21+00:00 | Vulnerability · Source |
| CVE-2021-47055 | suse_vex | SUSE CVE CVE-2021-47055 | known affected: 388 known not affected: 270 recommended: 227 | 2026-10-04T23:40:06+00:00 | Vulnerability · Source |
| CVE-2021-47311 | suse_vex | SUSE CVE CVE-2021-47311 | known affected: 453 known not affected: 276 recommended: 253 | 2026-10-04T23:40:02+00:00 | Vulnerability · Source |
| CVE-2021-47404 | suse_vex | SUSE CVE CVE-2021-47404 | known affected: 269 known not affected: 166 recommended: 685 | 2026-10-04T23:39:59+00:00 | Vulnerability · Source |
| CVE-2022-0617 | suse_vex | SUSE CVE CVE-2022-0617 | known affected: 207 known not affected: 2 recommended: 1629 | 2026-10-04T23:39:53+00:00 | Vulnerability · Source |
| CVE-2022-2991 | suse_vex | SUSE CVE CVE-2022-2991 | known affected: 394 known not affected: 59 recommended: 266 | 2026-10-04T23:39:49+00:00 | Vulnerability · Source |
| CVE-2022-3169 | suse_vex | SUSE CVE CVE-2022-3169 | known affected: 255 known not affected: 2 recommended: 1436 | 2026-10-04T23:39:47+00:00 | Vulnerability · Source |
| CVE-2022-36280 | suse_vex | SUSE CVE CVE-2022-36280 | known affected: 262 known not affected: 2 recommended: 1454 | 2026-10-04T23:39:36+00:00 | Vulnerability · Source |
| CVE-2022-39188 | suse_vex | SUSE CVE CVE-2022-39188 | known affected: 237 known not affected: 308 recommended: 1798 | 2026-10-04T23:39:34+00:00 | Vulnerability · Source |
| CVE-2022-40897 | suse_vex | SUSE CVE CVE-2022-40897 | known affected: 272 known not affected: 95 recommended: 348 | 2026-10-04T23:39:32+00:00 | Vulnerability · Source |
| CVE-2022-49080 | suse_vex | SUSE CVE CVE-2022-49080 | known affected: 506 known not affected: 81 recommended: 447 | 2026-10-04T23:39:24+00:00 | Vulnerability · Source |
| CVE-2022-49371 | suse_vex | SUSE CVE CVE-2022-49371 | known affected: 497 known not affected: 154 recommended: 377 | 2026-10-04T23:39:19+00:00 | Vulnerability · Source |
| CVE-2022-49542 | suse_vex | SUSE CVE CVE-2022-49542 | known affected: 376 known not affected: 311 recommended: 319 | 2026-10-04T23:39:15+00:00 | Vulnerability · Source |
| CVE-2022-49727 | suse_vex | SUSE CVE CVE-2022-49727 | known affected: 727 known not affected: 81 recommended: 40 | 2026-10-04T23:39:12+00:00 | Vulnerability · Source |
| CVE-2022-50220 | suse_vex | SUSE CVE CVE-2022-50220 | known affected: 497 known not affected: 243 recommended: 310 | 2026-10-04T23:39:05+00:00 | Vulnerability · Source |
| CVE-2022-50381 | suse_vex | SUSE CVE CVE-2022-50381 | known affected: 344 known not affected: 256 recommended: 384 | 2026-10-04T23:39:02+00:00 | Vulnerability · Source |
| CVE-2022-50755 | suse_vex | SUSE CVE CVE-2022-50755 | known affected: 548 known not affected: 178 recommended: 233 | 2026-10-04T23:38:57+00:00 | Vulnerability · Source |
| CVE-2023-4860 | suse_vex | SUSE CVE CVE-2023-4860 | recommended: 4 | 2026-10-04T23:38:50+00:00 | Vulnerability · Source |
| CVE-2023-6270 | suse_vex | SUSE CVE CVE-2023-6270 | known affected: 402 known not affected: 26 recommended: 1137 | 2026-10-04T23:38:46+00:00 | Vulnerability · Source |
| CVE-2023-46136 | suse_vex | SUSE CVE CVE-2023-46136 | known not affected: 111 recommended: 32 | 2026-10-04T23:38:37+00:00 | Vulnerability · Source |
| CVE-2023-52774 | suse_vex | SUSE CVE CVE-2023-52774 | known affected: 455 known not affected: 31 recommended: 875 | 2026-10-04T23:38:31+00:00 | Vulnerability · Source |
| CVE-2023-53596 | suse_vex | SUSE CVE CVE-2023-53596 | known affected: 651 known not affected: 93 recommended: 347 | 2026-10-04T23:38:22+00:00 | Vulnerability · Source |
| CVE-2024-10041 | suse_vex | SUSE CVE CVE-2024-10041 | known affected: 541 known not affected: 1 recommended: 714 | 2026-10-04T23:38:13+00:00 | Vulnerability · Source |
| CVE-2024-26668 | suse_vex | SUSE CVE CVE-2024-26668 | known affected: 486 known not affected: 6 recommended: 756 | 2026-10-04T23:38:09+00:00 | Vulnerability · Source |
| CVE-2024-35811 | suse_vex | SUSE CVE CVE-2024-35811 | known affected: 72 known not affected: 41 recommended: 917 | 2026-10-04T23:38:01+00:00 | Vulnerability · Source |
| CVE-2024-43806 | suse_vex | SUSE CVE CVE-2024-43806 | known affected: 75 known not affected: 648 recommended: 114 | 2026-10-04T23:37:50+00:00 | Vulnerability · Source |
| CVE-2024-43913 | suse_vex | SUSE CVE CVE-2024-43913 | known affected: 410 known not affected: 444 recommended: 280 | 2026-10-04T23:37:47+00:00 | Vulnerability · Source |
| CVE-2024-49940 | suse_vex | SUSE CVE CVE-2024-49940 | known affected: 826 known not affected: 34 recommended: 325 | 2026-10-04T23:37:40+00:00 | Vulnerability · Source |
| CVE-2024-49998 | suse_vex | SUSE CVE CVE-2024-49998 | known affected: 489 known not affected: 395 recommended: 286 | 2026-10-04T23:37:37+00:00 | Vulnerability · Source |
| CVE-2024-53103 | suse_vex | SUSE CVE CVE-2024-53103 | known affected: 574 known not affected: 237 recommended: 502 | 2026-10-04T23:37:32+00:00 | Vulnerability · Source |
| CVE-2024-53162 | suse_vex | SUSE CVE CVE-2024-53162 | known affected: 481 known not affected: 305 recommended: 468 | 2026-10-04T23:37:29+00:00 | Vulnerability · Source |
| CVE-2024-53208 | suse_vex | SUSE CVE CVE-2024-53208 | known affected: 364 known not affected: 417 recommended: 526 | 2026-10-04T23:37:27+00:00 | Vulnerability · Source |
| CVE-2024-53209 | suse_vex | SUSE CVE CVE-2024-53209 | known affected: 421 known not affected: 373 recommended: 459 | 2026-10-04T23:37:25+00:00 | Vulnerability · Source |
| CVE-2024-53229 | suse_vex | SUSE CVE CVE-2024-53229 | known affected: 364 known not affected: 430 recommended: 500 | 2026-10-04T23:37:24+00:00 | Vulnerability · Source |
| CVE-2024-56566 | suse_vex | SUSE CVE CVE-2024-56566 | known affected: 765 known not affected: 110 recommended: 401 | 2026-10-04T23:37:21+00:00 | Vulnerability · Source |
| CVE-2024-56567 | suse_vex | SUSE CVE CVE-2024-56567 | known affected: 515 known not affected: 278 recommended: 459 | 2026-10-04T23:37:19+00:00 | Vulnerability · Source |
| CVE-2024-56571 | suse_vex | SUSE CVE CVE-2024-56571 | known affected: 354 known not affected: 16 recommended: 468 | 2026-10-04T23:37:16+00:00 | Vulnerability · Source |
| CVE-2024-56572 | suse_vex | SUSE CVE CVE-2024-56572 | known affected: 666 known not affected: 221 recommended: 358 | 2026-10-04T23:37:14+00:00 | Vulnerability · Source |
| CVE-2024-56665 | suse_vex | SUSE CVE CVE-2024-56665 | known affected: 523 known not affected: 386 recommended: 358 | 2026-10-04T23:37:10+00:00 | Vulnerability · Source |
| CVE-2024-56667 | suse_vex | SUSE CVE CVE-2024-56667 | known affected: 394 known not affected: 494 recommended: 401 | 2026-10-04T23:37:08+00:00 | Vulnerability · Source |
| CVE-2024-56707 | suse_vex | SUSE CVE CVE-2024-56707 | known affected: 590 known not affected: 319 recommended: 358 | 2026-10-04T23:37:06+00:00 | Vulnerability · Source |
| CVE-2024-56715 | suse_vex | SUSE CVE CVE-2024-56715 | known affected: 590 known not affected: 319 recommended: 358 | 2026-10-04T23:37:04+00:00 | Vulnerability · Source |