October 2026 CVE archive
Records last modified in NIST NVD between Oct 1 and Oct 31, 2026 (UTC). Data imported from the NVD CVE API 2.0 and the CISA KEV catalog; each record shows its own source and verification time. The modified view only includes records that were CRITICAL or CISA-KEV-listed when imported — it is not a complete list of every modification.
Total records
24,591
Critical
3,297
High
7,976
Medium
7,646
Low
740
Severity not reported
4,932
In CISA KEV
191
Most affected vendors (by CPE data where available): microsoft (1424), google (825), linux (722), ibm (323), oracle (193), mozilla (182), adobe (165), broadcom (118), apache (116), fabian (98)
| CVE | Severity | CVSS | KEV | Vendor / product | Published | Modified |
|---|---|---|---|---|---|---|
| CVE-2026-112673 A type confusion issue was addressed with improved state handling. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112676 This issue was addressed with additional entitlement checks. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112679 A use-after-free issue was addressed with improved memory management. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112680 An out-of-bounds read was addressed with improved bounds checking. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112681 This issue was addressed with additional entitlement checks. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112682 An input validation issue was addressed with improved input validation. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112683 An out-of-bounds write issue was addressed with improved bounds checking. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112684 This issue was addressed through improved state management. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112686 A race condition was addressed with improved locking. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112687 This issue was addressed by removing the vulnerable code. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112689 An out-of-bounds write issue was addressed with improved input validation. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112690 This issue was addressed with improved input validation. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112691 An out-of-bounds write issue was addressed with improved input validation. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112692 This issue was addressed with additional entitlement checks. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112693 A use-after-free issue was addressed with improved memory management. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112695 A use-after-free issue was addressed with improved memory management. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112696 An out-of-bounds write issue was addressed with improved bounds checking. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112697 A use-after-free issue was addressed with improved memory management. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112698 The issue was addressed with improved memory handling. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112699 An out-of-bounds read was addressed with improved bounds checking. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112704 An information leakage was addressed with additional validation. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112705 An out-of-bounds write issue was addressed with improved bounds checking. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112707 A privacy issue was addressed by moving sensitive data to a protected location. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-113897 This issue was addressed by removing the vulnerable code. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-113898 A logging issue was addressed with improved data redaction. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-113899 The issue was addressed with improved checks. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-113900 A race condition was addressed with improved state handling. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-113901 A use-after-free issue was addressed with improved memory management. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-113903 A use-after-free issue was addressed with improved memory management. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-113904 A use-after-free issue was addressed with improved memory management. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-113906 A null pointer dereference was addressed with improved validation. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-113909 A memory corruption issue was addressed with improved input validation. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-113910 A memory initialization issue was addressed with improved memory handling. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-113915 A race condition was addressed with additional validation. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-113934 The issue was addressed with improved memory handling. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-113935 An out-of-bounds read was addressed with improved bounds checking. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-113936 An out-of-bounds read was addressed with improved bounds checking. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-113937 An out-of-bounds read was addressed with improved bounds checking. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-113938 An out-of-bounds read was addressed with improved bounds checking. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-113940 An out-of-bounds read was addressed with improved bounds checking. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
Sources: NIST NVD (CVE API 2.0) and the CISA KEV catalog. Severity is as stated by the source; missing values are shown as “not reported”, never estimated.