| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2025-34951 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34950 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34949 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34948 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34947 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34946 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34945 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34944 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34943 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34942 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34941 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34940 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34939 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34938 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34937 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34936 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34935 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34934 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34933 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34932 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34931 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34930 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34929 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34928 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34927 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34926 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34925 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34924 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34923 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34922 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34921 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34920 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34919 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34918 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34917 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34916 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34915 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34914 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34913 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34912 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34911 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34910 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34909 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34908 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34907 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34906 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34905 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34904 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34903 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||
| CVE-2025-34902 | — | 0.00 | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
- CVE-2025-34951Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34950Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34949Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34948Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34947Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34946Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34945Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34944Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34943Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34942Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34941Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34940Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34939Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34938Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34937Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34936Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34935Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34934Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34933Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34932Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34931Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34930Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34929Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34928Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34927Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34926Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34925Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34924Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34923Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34922Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34921Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34920Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34919Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34918Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34917Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34916Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34915Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34914Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34913Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34912Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34911Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34910Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34909Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34908Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34907Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34906Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34905Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34904Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34903Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.
- CVE-2025-34902Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.