| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| 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-34751 | — | 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-34750 | — | 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-34749 | — | 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-34748 | — | 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-34747 | — | 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-34746 | — | 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-34745 | — | 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-34744 | — | 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-34743 | — | 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-34742 | — | 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-34741 | — | 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-34740 | — | 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-34739 | — | 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-34738 | — | 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-34737 | — | 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-34736 | — | 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-34735 | — | 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-34734 | — | 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-34733 | — | 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-34732 | — | 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-34731 | — | 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-34730 | — | 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-34729 | — | 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-34728 | — | 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-34727 | — | 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-34726 | — | 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-34725 | — | 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-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.
- CVE-2025-34751Jan 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-34750Jan 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-34749Jan 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-34748Jan 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-34747Jan 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-34746Jan 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-34745Jan 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-34744Jan 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-34743Jan 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-34742Jan 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-34741Jan 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-34740Jan 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-34739Jan 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-34738Jan 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-34737Jan 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-34736Jan 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-34735Jan 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-34734Jan 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-34733Jan 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-34732Jan 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-34731Jan 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-34730Jan 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-34729Jan 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-34728Jan 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-34727Jan 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-34726Jan 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-34725Jan 2, 2026risk 0.00cvss —epss —
Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.