VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291026 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49537 | suse_vex | SUSE CVE CVE-2022-49537 | known affected: 360 known not affected: 218 recommended: 361 | 2026-08-14T01:20:49+00:00 | Vulnerability · Source |
| CVE-2022-49544 | suse_vex | SUSE CVE CVE-2022-49544 | known affected: 427 known not affected: 149 recommended: 333 | 2026-08-14T01:20:48+00:00 | Vulnerability · Source |
| CVE-2022-49555 | suse_vex | SUSE CVE CVE-2022-49555 | known affected: 409 known not affected: 220 recommended: 333 | 2026-08-14T01:20:47+00:00 | Vulnerability · Source |
| CVE-2022-49559 | suse_vex | SUSE CVE CVE-2022-49559 | known affected: 334 known not affected: 294 recommended: 265 | 2026-08-14T01:20:45+00:00 | Vulnerability · Source |
| CVE-2022-49581 | suse_vex | SUSE CVE CVE-2022-49581 | known affected: 461 known not affected: 142 recommended: 263 | 2026-08-14T01:20:42+00:00 | Vulnerability · Source |
| CVE-2022-49589 | suse_vex | SUSE CVE CVE-2022-49589 | known affected: 570 known not affected: 147 recommended: 67 | 2026-08-14T01:20:41+00:00 | Vulnerability · Source |
| CVE-2022-49595 | suse_vex | SUSE CVE CVE-2022-49595 | known not affected: 147 recommended: 27 | 2026-08-14T01:20:39+00:00 | Vulnerability · Source |
| CVE-2022-49607 | suse_vex | SUSE CVE CVE-2022-49607 | known affected: 455 known not affected: 148 recommended: 263 | 2026-08-14T01:20:37+00:00 | Vulnerability · Source |
| CVE-2022-49609 | suse_vex | SUSE CVE CVE-2022-49609 | known affected: 399 known not affected: 243 recommended: 293 | 2026-08-14T01:20:35+00:00 | Vulnerability · Source |
| CVE-2022-49616 | suse_vex | SUSE CVE CVE-2022-49616 | known affected: 371 known not affected: 257 recommended: 243 | 2026-08-14T01:20:34+00:00 | Vulnerability · Source |
| CVE-2022-49617 | suse_vex | SUSE CVE CVE-2022-49617 | known affected: 371 known not affected: 257 recommended: 223 | 2026-08-14T01:20:32+00:00 | Vulnerability · Source |
| CVE-2022-49623 | suse_vex | SUSE CVE CVE-2022-49623 | known affected: 395 known not affected: 344 recommended: 360 | 2026-08-14T01:20:29+00:00 | Vulnerability · Source |
| CVE-2022-49625 | suse_vex | SUSE CVE CVE-2022-49625 | known affected: 458 known not affected: 148 recommended: 302 | 2026-08-14T01:20:27+00:00 | Vulnerability · Source |
| CVE-2022-49628 | suse_vex | SUSE CVE CVE-2022-49628 | known affected: 334 known not affected: 294 recommended: 223 | 2026-08-14T01:20:25+00:00 | Vulnerability · Source |
| CVE-2022-49631 | suse_vex | SUSE CVE CVE-2022-49631 | known affected: 348 known not affected: 256 recommended: 320 | 2026-08-14T01:20:23+00:00 | Vulnerability · Source |
| CVE-2022-49643 | suse_vex | SUSE CVE CVE-2022-49643 | known affected: 348 known not affected: 256 recommended: 334 | 2026-08-14T01:20:21+00:00 | Vulnerability · Source |
| CVE-2022-49647 | suse_vex | SUSE CVE CVE-2022-49647 | known affected: 409 known not affected: 218 recommended: 380 | 2026-08-14T01:20:18+00:00 | Vulnerability · Source |
| CVE-2022-49649 | suse_vex | SUSE CVE CVE-2022-49649 | known affected: 395 known not affected: 183 recommended: 319 | 2026-08-14T01:20:16+00:00 | Vulnerability · Source |
| CVE-2022-49674 | suse_vex | SUSE CVE CVE-2022-49674 | known affected: 395 known not affected: 381 recommended: 353 | 2026-08-14T01:20:14+00:00 | Vulnerability · Source |
| CVE-2022-49677 | suse_vex | SUSE CVE CVE-2022-49677 | known affected: 450 known not affected: 220 recommended: 223 | 2026-08-14T01:20:12+00:00 | Vulnerability · Source |
| CVE-2022-49683 | suse_vex | SUSE CVE CVE-2022-49683 | known affected: 334 known not affected: 294 recommended: 223 | 2026-08-14T01:20:11+00:00 | Vulnerability · Source |
| CVE-2022-49687 | suse_vex | SUSE CVE CVE-2022-49687 | known affected: 365 known not affected: 213 recommended: 348 | 2026-08-14T01:20:09+00:00 | Vulnerability · Source |
| CVE-2022-49694 | suse_vex | SUSE CVE CVE-2022-49694 | known affected: 364 known not affected: 301 recommended: 100 | 2026-08-14T01:20:07+00:00 | Vulnerability · Source |
| CVE-2022-49695 | suse_vex | SUSE CVE CVE-2022-49695 | known affected: 371 known not affected: 258 recommended: 265 | 2026-08-14T01:20:06+00:00 | Vulnerability · Source |
| CVE-2022-49697 | suse_vex | SUSE CVE CVE-2022-49697 | known affected: 470 known not affected: 192 recommended: 142 | 2026-08-14T01:20:04+00:00 | Vulnerability · Source |
| CVE-2022-49708 | suse_vex | SUSE CVE CVE-2022-49708 | known affected: 395 known not affected: 181 recommended: 387 | 2026-08-14T01:20:02+00:00 | Vulnerability · Source |
| CVE-2022-49713 | suse_vex | SUSE CVE CVE-2022-49713 | known affected: 334 known not affected: 242 recommended: 319 | 2026-08-14T01:20:00+00:00 | Vulnerability · Source |
| CVE-2022-49726 | suse_vex | SUSE CVE CVE-2022-49726 | known affected: 389 known not affected: 211 recommended: 270 | 2026-08-14T01:19:58+00:00 | Vulnerability · Source |
| CVE-2022-49729 | suse_vex | SUSE CVE CVE-2022-49729 | known affected: 427 known not affected: 200 recommended: 330 | 2026-08-14T01:19:57+00:00 | Vulnerability · Source |
| CVE-2026-56746 | redhat_vex | io.netty/netty-codec-http: Netty: Security control bypass allows unauthorized requests via null origin header | fixed: 5 known affected: 54 known not affected: 1 | 2026-08-14T01:19:56+00:00 | Vulnerability · Source |
| CVE-2022-49732 | suse_vex | SUSE CVE CVE-2022-49732 | known affected: 419 known not affected: 243 recommended: 142 | 2026-08-14T01:19:55+00:00 | Vulnerability · Source |
| CVE-2022-49746 | suse_vex | SUSE CVE CVE-2022-49746 | known affected: 385 known not affected: 196 recommended: 251 | 2026-08-14T01:19:53+00:00 | Vulnerability · Source |
| CVE-2022-49748 | suse_vex | SUSE CVE CVE-2022-49748 | known affected: 334 known not affected: 137 recommended: 251 | 2026-08-14T01:19:52+00:00 | Vulnerability · Source |
| CVE-2022-49752 | suse_vex | SUSE CVE CVE-2022-49752 | known not affected: 344 recommended: 49 | 2026-08-14T01:19:50+00:00 | Vulnerability · Source |
| CVE-2022-49756 | suse_vex | SUSE CVE CVE-2022-49756 | known not affected: 344 | 2026-08-14T01:19:48+00:00 | Vulnerability · Source |
| CVE-2022-49761 | suse_vex | SUSE CVE CVE-2022-49761 | known affected: 506 known not affected: 204 recommended: 37 | 2026-08-14T01:19:46+00:00 | Vulnerability · Source |
| CVE-2022-49762 | suse_vex | SUSE CVE CVE-2022-49762 | known affected: 546 known not affected: 169 recommended: 92 | 2026-08-14T01:19:45+00:00 | Vulnerability · Source |
| CVE-2022-49768 | suse_vex | SUSE CVE CVE-2022-49768 | known affected: 643 known not affected: 152 recommended: 23 | 2026-08-14T01:19:43+00:00 | Vulnerability · Source |
| CVE-2022-49769 | suse_vex | SUSE CVE CVE-2022-49769 | known affected: 406 known not affected: 184 recommended: 316 | 2026-08-14T01:19:42+00:00 | Vulnerability · Source |
| CVE-2022-49772 | suse_vex | SUSE CVE CVE-2022-49772 | known affected: 424 known not affected: 165 recommended: 318 | 2026-08-14T01:19:40+00:00 | Vulnerability · Source |
| CVE-2022-49786 | suse_vex | SUSE CVE CVE-2022-49786 | known affected: 369 known not affected: 343 recommended: 92 | 2026-08-14T01:19:38+00:00 | Vulnerability · Source |
| CVE-2022-49797 | suse_vex | SUSE CVE CVE-2022-49797 | known affected: 339 known not affected: 294 recommended: 214 | 2026-08-14T01:19:37+00:00 | Vulnerability · Source |
| CVE-2022-49806 | suse_vex | SUSE CVE CVE-2022-49806 | known affected: 112 known not affected: 285 | 2026-08-14T01:19:35+00:00 | Vulnerability · Source |
| CVE-2022-49809 | suse_vex | SUSE CVE CVE-2022-49809 | known affected: 420 known not affected: 187 recommended: 281 | 2026-08-14T01:19:34+00:00 | Vulnerability · Source |
| CVE-2022-49820 | suse_vex | SUSE CVE CVE-2022-49820 | known not affected: 397 | 2026-08-14T01:19:32+00:00 | Vulnerability · Source |
| CVE-2022-49826 | suse_vex | SUSE CVE CVE-2022-49826 | known affected: 404 known not affected: 172 recommended: 304 | 2026-08-14T01:19:31+00:00 | Vulnerability · Source |
| CVE-2022-49835 | suse_vex | SUSE CVE CVE-2022-49835 | known affected: 418 known not affected: 174 recommended: 318 | 2026-08-14T01:19:29+00:00 | Vulnerability · Source |
| CVE-2022-49836 | suse_vex | SUSE CVE CVE-2022-49836 | known affected: 353 known not affected: 250 recommended: 281 | 2026-08-14T01:19:27+00:00 | Vulnerability · Source |
| CVE-2022-49839 | suse_vex | SUSE CVE CVE-2022-49839 | known affected: 424 known not affected: 150 recommended: 310 | 2026-08-14T01:19:26+00:00 | Vulnerability · Source |
| CVE-2022-49842 | suse_vex | SUSE CVE CVE-2022-49842 | known affected: 422 known not affected: 158 recommended: 318 | 2026-08-14T01:19:24+00:00 | Vulnerability · Source |