October 2026 CVE archive
Records published in NIST NVD between Oct 1 and Oct 30, 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.
Total records
17,181
Critical
1,306
High
5,739
Medium
6,115
Low
636
Severity not reported
3,385
In CISA KEV
19
Most affected vendors (by CPE data where available): microsoft (1303), google (745), oracle (156), ibm (140), adobe (129), broadcom (61), langflow (57), apache (45), freerdp (42), linuxfoundation (41)
| CVE | Severity | CVSS | KEV | Vendor / product | Published | Modified |
|---|---|---|---|---|---|---|
| CVE-2026-113900 A race condition was addressed with improved state handling. |
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-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-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-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-112676 This issue was addressed with additional entitlement checks. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112677 An authorization issue was addressed with improved access control. |
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-112668 A logic issue was addressed with improved checks. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112669 A race condition was addressed with improved state handling. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112670 An out-of-bounds write issue was addressed with improved input validation. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112671 A resource exhaustion issue was addressed with improved input validation. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112672 The issue was addressed with improved checks. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112673 A type confusion issue was addressed with improved state handling. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112656 An out-of-bounds read was addressed with improved bounds checking. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112660 An authorization issue was addressed with improved state management. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112665 An information disclosure issue was addressed with improved state management. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112666 A use-after-free issue was addressed with improved memory management. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112647 An access issue was addressed with additional sandbox restrictions. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112652 A logic issue was addressed with improved state management. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112653 A use-after-free issue was addressed with improved memory management. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112654 A use-after-free issue was addressed with improved memory management. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112638 A heap buffer overflow was addressed with improved bounds checking. |
not reported | — | — | — | 2026-10-26 | 2026-10-27 |
| CVE-2026-112639 A use-after-free issue was addressed with improved memory management. |
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.