Total
336347 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2025-46304 | 1 Apple | 3 Ipados, Iphone Os, Macos | 2026-02-13 | N/A | 5.7 MEDIUM |
|
The issue was addressed with improved bounds checks. This issue is fixed in macOS Sequoia 15.7.4, iOS 18.7.5 and iPadOS 18.7.5, macOS Sonoma 14.8.4. A malicious HID device may cause an unexpected process crash.
|
|||||
| CVE-2025-46303 | 1 Apple | 3 Ipados, Iphone Os, Macos | 2026-02-13 | N/A | 5.7 MEDIUM |
|
The issue was addressed with improved bounds checks. This issue is fixed in macOS Sequoia 15.7.4, iOS 18.7.5 and iPadOS 18.7.5, macOS Sonoma 14.8.4. A malicious HID device may cause an unexpected process crash.
|
|||||
| CVE-2025-46302 | 1 Apple | 3 Ipados, Iphone Os, Macos | 2026-02-13 | N/A | 5.7 MEDIUM |
|
The issue was addressed with improved bounds checks. This issue is fixed in macOS Sequoia 15.7.4, iOS 18.7.5 and iPadOS 18.7.5, macOS Sonoma 14.8.4. A malicious HID device may cause an unexpected process crash.
|
|||||
| CVE-2025-46301 | 1 Apple | 3 Ipados, Iphone Os, Macos | 2026-02-13 | N/A | 5.7 MEDIUM |
|
The issue was addressed with improved bounds checks. This issue is fixed in macOS Sequoia 15.7.4, iOS 18.7.5 and iPadOS 18.7.5, macOS Sonoma 14.8.4. A malicious HID device may cause an unexpected process crash.
|
|||||
| CVE-2025-46300 | 1 Apple | 3 Ipados, Iphone Os, Macos | 2026-02-13 | N/A | 5.7 MEDIUM |
|
The issue was addressed with improved bounds checks. This issue is fixed in macOS Sequoia 15.7.4, iOS 18.7.5 and iPadOS 18.7.5, macOS Sonoma 14.8.4. A malicious HID device may cause an unexpected process crash.
|
|||||
| CVE-2025-36552 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-36545 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-36542 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-36538 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-36534 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-36532 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-36526 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-36524 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-36523 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-36517 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-35997 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-35993 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-35976 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-35962 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-35961 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-35960 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-32734 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-32733 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-32090 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-32085 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-32082 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-32009 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-31942 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-31364 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-31358 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-31145 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-30517 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-29869 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-27941 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-27928 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-27573 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-27569 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-27251 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-26471 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||
| CVE-2025-25049 | 2026-02-13 | N/A | N/A | ||
|
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
|
|||||