| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2025-34801 | — | 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-34800 | — | 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-34799 | — | 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-34798 | — | 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-34797 | — | 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-34796 | — | 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-34795 | — | 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-34794 | — | 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-34793 | — | 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-34792 | — | 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-34791 | — | 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-34790 | — | 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-34789 | — | 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-34788 | — | 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-34787 | — | 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-34786 | — | 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-34785 | — | 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-34784 | — | 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-34783 | — | 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-34782 | — | 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-34781 | — | 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-34780 | — | 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-34779 | — | 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-34778 | — | 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-34777 | — | 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-34776 | — | 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-34775 | — | 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-34774 | — | 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-34773 | — | 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-34772 | — | 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-34771 | — | 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-34770 | — | 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-34769 | — | 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-34768 | — | 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-34767 | — | 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-34766 | — | 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-34765 | — | 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-34764 | — | 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-34763 | — | 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-34762 | — | 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-34761 | — | 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-34760 | — | 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-34759 | — | 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-34758 | — | 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-34757 | — | 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-34756 | — | 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-34755 | — | 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-34754 | — | 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-34753 | — | 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-34752 | — | 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-34801Jan 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-34800Jan 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-34799Jan 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-34798Jan 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-34797Jan 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-34796Jan 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-34795Jan 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-34794Jan 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-34793Jan 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-34792Jan 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-34791Jan 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-34790Jan 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-34789Jan 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-34788Jan 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-34787Jan 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-34786Jan 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-34785Jan 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-34784Jan 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-34783Jan 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-34782Jan 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-34781Jan 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-34780Jan 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-34779Jan 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-34778Jan 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-34777Jan 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-34776Jan 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-34775Jan 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-34774Jan 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-34773Jan 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-34772Jan 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-34771Jan 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-34770Jan 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-34769Jan 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-34768Jan 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-34767Jan 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-34766Jan 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-34765Jan 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-34764Jan 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-34763Jan 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-34762Jan 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-34761Jan 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-34760Jan 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-34759Jan 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-34758Jan 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-34757Jan 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-34756Jan 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-34755Jan 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-34754Jan 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-34753Jan 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-34752Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.