What CISA added in the last seven days, and the weakness behind each.
8 vulnerabilities were added to CISA's exploited list from 26 Oct to 29 October 2026; 5 are due within three days or already late. This page rebuilds itself after each refresh of our knowledge graph, so it moves without anyone writing it. The reasoning and the fix steps are in the dated notes beside it.
- CVE-2026-97229GitLab Community Edition and Enterprise EditionAdded 29 Oct, due 1 NovWeakness: CWE-190 Integer Overflow or WraparoundTodayCVSS10.0EPSS0.27
- CVE-2026-76418Cisco Secure Firewall ASA Software and Cisco Secure FTD SoftwareAdded 29 Oct, due 1 NovWeakness: CWE-690 Unchecked Return Value to NULL Pointer DereferenceTodayCVSS8.6EPSS0.01
- CVE-2026-46300Linux KernelAdded 28 Oct, due 31 Oct · our note and PDFWeakness: CWE-456 Missing Initialization of a VariableTodayCVSS7.8EPSS0.16
- CVE-2026-109619PHP Group PHPAdded 26 Oct, due 29 Oct · our note and PDFTodayCVSS8.1EPSS1.00
- CVE-2026-109618PHP Group PHPAdded 26 Oct, due 29 Oct · our note and PDFTodayCVSS9.8EPSS1.00
- CVE-2026-48356Adobe Commerce and MagentoAdded 27 Oct, due 10 Nov · our note and PDFWeakness: CWE-434 Unrestricted Upload of File with Dangerous TypeThis weekCVSS9.3EPSS0.45
- CVE-2026-111497Google BrotliAdded 27 Oct, due 10 Nov · our note and PDFThis weekCVSS9.8EPSS0.83
- CVE-2026-41709Broadcom VMware ESXAdded 28 Oct, due 11 Nov · our note and PDFWeakness: CWE-778 Insufficient LoggingNext patch cycleCVSS2.7EPSS0.01
Updated 30 October 2026 at 16:39 UTC. Entries and due dates are CISA's, as loaded into our graph; CVSS is the base score on the NVD record (version 3.x), so it can differ from the score in our notes, which quote the highest on the CVE record, often version 4.0; EPSS is FIRST's probability of exploitation in the next 30 days; a score the record does not have yet says so instead of showing 0. Rule: Today when the CISA due date has passed or is within three days; This week when EPSS is 0.40 or more; otherwise next patch cycle. A rule of thumb, not a verdict on your estate.
The weaknesses behind them
A weakness class (a CWE) is the kind of mistake in the code. Seeing the same class in several entries is the useful signal: it is where a review of your own software or your suppliers pays most.
- CWE-416Use After Free
In 2 of this week's 8.
- CWE-755Improper Handling of Exceptional Conditions
In 2 of this week's 8.
- CWE-824Access of Uninitialized Pointer
In 2 of this week's 8.
- CWE-1325Improperly Controlled Sequential Memory Allocation
In 2 of this week's 8.
- CWE-1419Incorrect Initialization of Resource
In 2 of this week's 8.
- CWE-190Integer Overflow or Wraparound
In 1 of this week's 8. Read our note on CWE-190.
- CWE-252Unchecked Return Value
In 1 of this week's 8. Our note that covers it: Brotli CVE-2026-111497: a decompression bug in a library you did not know you shipped.
- CWE-434Unrestricted Upload of File with Dangerous Type
In 1 of this week's 8. Our note that covers it: Adobe Commerce CVE-2026-48356: patched in July, on CISA's exploited list in October.
- CWE-456Missing Initialization of a Variable
In 1 of this week's 8. Read our note on CWE-456.
- CWE-690Unchecked Return Value to NULL Pointer Dereference
In 1 of this week's 8. Read our note on CWE-690.
- CWE-778Insufficient Logging
In 1 of this week's 8. Read our note on CWE-778.
- CWE-787Out-of-bounds Write
In 1 of this week's 8; 6 of the 108 added in the last 90 days (was 2 in the 90 before). Read our note on CWE-787.
Start with one piece of work.
Give us one piece of work and read access to one system. We map it and come back with what we found, what we would build and what it would take — before any commitment. You decide using our output, not our pitch.
Talk to us