Vulnerabilities
Structured data from NIST NVD and the CISA KEV catalog. Fields the source has not provided are shown as such — nothing is inferred.
Archives: September 2026 October 2026 CISA KEV / threat intelligence
| CVE | Severity | CVSS | KEV | Description | Modified (UTC) |
|---|---|---|---|---|---|
| CVE-2025-34573 | not reported | — | No | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 2026-11-07 |
| CVE-2025-34572 | not reported | — | No | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 2026-11-07 |
| CVE-2025-34571 | not reported | — | No | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 2026-11-07 |
| CVE-2025-34570 | not reported | — | No | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 2026-11-07 |
| CVE-2025-34569 | not reported | — | No | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 2026-11-07 |
| CVE-2025-34568 | not reported | — | No | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 2026-11-07 |
| CVE-2025-34567 | not reported | — | No | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 2026-11-07 |
| CVE-2025-34566 | not reported | — | No | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 2026-11-07 |
| CVE-2025-34565 | not reported | — | No | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 2026-11-07 |
| CVE-2025-34564 | not reported | — | No | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 2026-11-07 |
| CVE-2025-34563 | not reported | — | No | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 2026-11-07 |
| CVE-2025-22196 | not reported | — | No | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. | 2026-11-07 |
| CVE-2025-22195 | not reported | — | No | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. | 2026-11-07 |
| CVE-2025-22194 | not reported | — | No | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. | 2026-11-07 |
| CVE-2025-22193 | not reported | — | No | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. | 2026-11-07 |
| CVE-2025-22192 | not reported | — | No | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. | 2026-11-07 |
| CVE-2025-22191 | not reported | — | No | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. | 2026-11-07 |
| CVE-2025-22190 | not reported | — | No | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. | 2026-11-07 |
| CVE-2025-22189 | not reported | — | No | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. | 2026-11-07 |
| CVE-2025-22188 | not reported | — | No | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. | 2026-11-07 |

