| CVE-2021-44784 | Rejected reason: Not used | No Score | 2026-10-15 |
| CVE-2021-44783 | Rejected reason: Not used | No Score | 2026-10-15 |
| CVE-2021-44782 | Rejected reason: Not used | No Score | 2026-10-15 |
| CVE-2021-44781 | Rejected reason: Not used | No Score | 2026-10-15 |
| CVE-2021-44780 | Rejected reason: Not used | No Score | 2026-10-15 |
| CVE-2021-4476 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | No Score | 2026-10-15 |
| CVE-2021-4475 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | No Score | 2026-10-15 |
| CVE-2021-4454 | In the Linux kernel, the following vulnerability has been resolved: can: j1939: fix errant WARN_ON_ONCE in j1939_session_deactivate The conclusion "j1939_session_deactivate() should be called with a session ref-count of at least 2" is incorrect. In some concurrent scenarios, j1939_session_deactivate can be called with the session ref-count less than 2. But there is not any problem because it will check the session active state before session putting in j1939_session_deactivate_locked(). Here is the concurrent scenario of the problem reported by syzbot and my reproduction log. cpu0 cpu1 j1939_xtp_rx_eoma j1939_xtp_rx_abort_one j1939_session_get_by_addr [kref == 2] j1939_session_get_by_addr [kref == 3] j1939_session_deactivate [kref == 2] j1939_session_put [kref == 1] j1939_session_completed j1939_session_deactivate WARN_ON_ONCE(kref < 2) ===================================================== WARNING: CPU: 1 PID: 21 at net/can/j1939/transport.c:1088 j1939_session_deactivate+0x5f/0x70 CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted 5.14.0-rc7+ #32 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1 04/01/2014 RIP: 0010:j1939_session_deactivate+0x5f/0x70 Call Trace: j1939_session_deactivate_activate_next+0x11/0x28 j1939_xtp_rx_eoma+0x12a/0x180 j1939_tp_recv+0x4a2/0x510 j1939_can_recv+0x226/0x380 can_rcv_filter+0xf8/0x220 can_receive+0x102/0x220 ? process_backlog+0xf0/0x2c0 can_rcv+0x53/0xf0 __netif_receive_skb_one_core+0x67/0x90 ? process_backlog+0x97/0x2c0 __netif_receive_skb+0x22/0x80 | medium | 2026-10-15 |
| CVE-2021-44175 | Rejected reason: Not used | No Score | 2026-10-15 |
| CVE-2021-44174 | Rejected reason: Not used | No Score | 2026-10-15 |
| CVE-2021-44173 | Rejected reason: Not used | No Score | 2026-10-15 |
| CVE-2021-43079 | Rejected reason: Not used | No Score | 2026-10-15 |
| CVE-2021-43078 | Rejected reason: Not used | No Score | 2026-10-15 |
| CVE-2021-43069 | Rejected reason: Not used | No Score | 2026-10-15 |
| CVE-2021-32601 | Rejected reason: Not used | No Score | 2026-10-15 |
| CVE-2021-0447 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | No Score | 2026-10-15 |
| CVE-2021-0323 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | No Score | 2026-10-15 |
| CVE-2020-6645 | Rejected reason: Not used | No Score | 2026-10-15 |
| CVE-2020-37281 | Gravitee API Management through 4.12.22 contains an authentication bypass vulnerability that allows unauthenticated remote attackers to impersonate any user by forging JWTs signed with the shipped default jwt.secret. Attackers knowing an existing user ID can sign an HS256 token with that subject and present it as a bearer token to the Management API, impersonating administrators to gain full platform control. | critical | 2026-10-15 |
| CVE-2020-0436 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | No Score | 2026-10-15 |
| CVE-2020-0402 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | No Score | 2026-10-15 |
| CVE-2020-0040 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | No Score | 2026-10-15 |
| CVE-2019-6185 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | No Score | 2026-10-15 |
| CVE-2019-6174 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | No Score | 2026-10-15 |
| CVE-2019-6164 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | No Score | 2026-10-15 |
| CVE-2019-6162 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | No Score | 2026-10-15 |
| CVE-2019-25725 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | No Score | 2026-10-15 |
| CVE-2019-25715 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | No Score | 2026-10-15 |
| CVE-2019-25685 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | high | 2026-10-15 |
| CVE-2019-25348 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | high | 2026-10-15 |
| CVE-2019-25161 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | No Score | 2026-10-15 |
| CVE-2019-19761 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | No Score | 2026-10-15 |
| CVE-2019-19760 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | No Score | 2026-10-15 |
| CVE-2019-19759 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | No Score | 2026-10-15 |
| CVE-2018-9204 | Rejected reason: Not used | No Score | 2026-10-15 |
| CVE-2018-9203 | Rejected reason: Not used | No Score | 2026-10-15 |
| CVE-2018-9202 | Rejected reason: Not used | No Score | 2026-10-15 |
| CVE-2018-9201 | Rejected reason: Not used | No Score | 2026-10-15 |
| CVE-2018-9200 | Rejected reason: Not used | No Score | 2026-10-15 |
| CVE-2018-9199 | Rejected reason: Not used | No Score | 2026-10-15 |
| CVE-2018-9198 | Rejected reason: Not used | No Score | 2026-10-15 |
| CVE-2018-9197 | Rejected reason: Not used | No Score | 2026-10-15 |
| CVE-2018-9196 | Rejected reason: Not used | No Score | 2026-10-15 |
| CVE-2018-8014 | The defaults settings for the CORS filter provided in Apache Tomcat 9.0.0.M1 to 9.0.8, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, 7.0.41 to 7.0.88 are insecure and enable 'supportsCredentials' for all origins. It is expected that users of the CORS filter will have configured it appropriately for their environment rather than using it in the default configuration. Therefore, it is expected that most users will not be impacted by this issue. | critical | 2026-10-15 |
| CVE-2018-7489 | FasterXML jackson-databind before 2.7.9.3, 2.8.x before 2.8.11.1 and 2.9.x before 2.9.5 allows unauthenticated remote code execution because of an incomplete fix for the CVE-2017-7525 deserialization flaw. This is exploitable by sending maliciously crafted JSON input to the readValue method of the ObjectMapper, bypassing a blacklist that is ineffective if the c3p0 libraries are available in the classpath. | critical | 2026-10-15 |
| CVE-2018-2811 | Vulnerability in the Java SE component of Oracle Java SE (subcomponent: Install). Supported versions that are affected are Java SE: 8u162 and 10. Difficult to exploit vulnerability allows unauthenticated attacker with logon to the infrastructure where Java SE executes to compromise Java SE. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Java SE, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Java SE. Note: Applies to installation process on client deployment of Java. CVSS 3.0 Base Score 7.7 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H). | high | 2026-10-15 |
| CVE-2018-20786 | libvterm through 0+bzr726, as used in Vim and other products, mishandles certain out-of-memory conditions, leading to a denial of service (application crash), related to screen.c, state.c, and vterm.c. | high | 2026-10-15 |
| CVE-2018-20406 | Modules/_pickle.c in Python before 3.7.1 has an integer overflow via a large LONG_BINPUT value that is mishandled during a "resize to twice the size" attempt. This issue might cause memory exhaustion, but is only relevant if the pickle format is used for serializing tens or hundreds of gigabytes of data. This issue is fixed in: v3.4.10, v3.4.10rc1; v3.5.10, v3.5.10rc1, v3.5.7, v3.5.7rc1, v3.5.8, v3.5.8rc1, v3.5.8rc2, v3.5.9; v3.6.10, v3.6.10rc1, v3.6.11, v3.6.11rc1, v3.6.12, v3.6.7, v3.6.7rc1, v3.6.7rc2, v3.6.8, v3.6.8rc1, v3.6.9, v3.6.9rc1; v3.7.1, v3.7.1rc1, v3.7.1rc2, v3.7.2, v3.7.2rc1, v3.7.3, v3.7.3rc1, v3.7.4, v3.7.4rc1, v3.7.4rc2, v3.7.5, v3.7.5rc1, v3.7.6, v3.7.6rc1, v3.7.7, v3.7.7rc1, v3.7.8, v3.7.8rc1, v3.7.9. | high | 2026-10-15 |
| CVE-2018-19876 | cairo 1.16.0, in cairo_ft_apply_variations() in cairo-ft-font.c, would free memory using a free function incompatible with WebKit's fastMalloc, leading to an application crash with a "free(): invalid pointer" error. | medium | 2026-10-15 |
| CVE-2018-19857 | The CAF demuxer in modules/demux/caf.c in VideoLAN VLC media player 3.0.4 may read memory from an uninitialized pointer when processing magic cookies in CAF files, because a ReadKukiChunk() cast converts a return value to an unsigned int even if that value is negative. This could result in a denial of service and/or a potential infoleak. | critical | 2026-10-15 |