Vulnerabilities
Aggregated CVE / GHSA / KEV / OSV — filter by tag and category.
| ID | Title | |
|---|---|---|
| CVE-2026-21019 |
|
Vulnerability in CVE-2026-21019 (CVE-2026-21019)
vulnerability in CVE-2026-21019 (CVE-2026-21019). Risk of unauthorized operations or information disclosure.
|
| CVE-2026-21018 |
|
Out-of-Bounds Write in samsung (CVE-2026-21018)
out-of-bounds write in samsung (CVE-2026-21018). Successful exploitation can lead to full system takeover.
|
| CVE-2025-14033 |
|
Vulnerability in wordpress (CVE-2025-14033)
vulnerability in wordpress (CVE-2025-14033). Risk of unauthorized operations or information disclosure.
|
| CVE-2025-11159 |
|
Vulnerability in hitachi (CVE-2025-11159)
vulnerability in hitachi (CVE-2025-11159). Successful exploitation can lead to full system takeover.
|
| BELL-CVE-2026-43894 |
|
BELL-CVE-2026-43894 |
| BELL-CVE-2026-42257 |
|
BELL-CVE-2026-42257 |
| BELL-CVE-2026-4892 |
|
BELL-CVE-2026-4892 |
| BELL-CVE-2026-4893 |
|
BELL-CVE-2026-4893 |
| BELL-CVE-2026-5172 |
|
BELL-CVE-2026-5172 |
| BELL-CVE-2026-4890 |
|
BELL-CVE-2026-4890 |
| BELL-CVE-2026-2291 |
|
BELL-CVE-2026-2291 |
| BELL-CVE-2026-4891 |
|
BELL-CVE-2026-4891 |
| RLSA-2026:16055 |
|
Vulnerability in libtiff (RLSA-2026:16055)
vulnerability in libtiff (RLSA-2026:16055). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `0:4.0.9-37.el8_10` or later.
|
| RLSA-2026:16019 |
|
Vulnerability in freerdp (RLSA-2026:16019)
vulnerability in freerdp (RLSA-2026:16019). Risk of unauthorized operations or information disclosure. Exploitable via ``nBlockAlign``. Mitigation: upgrade to `2:2.11.7-9.el8_10` or later.
|
| RLSA-2026:15953 |
|
Vulnerability in glib2 (RLSA-2026:15953)
vulnerability in glib2 (RLSA-2026:15953). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `0:2.56.4-169.el8_10` or later.
|
| MAL-2026-3638 |
|
Vulnerability in openai-spellcheckers (MAL-2026-3638)
vulnerability in openai-spellcheckers (MAL-2026-3638). Risk of unauthorized operations or information disclosure.
|
| MAL-2026-3688 |
|
Vulnerability in d4rktg (MAL-2026-3688)
vulnerability in d4rktg (MAL-2026-3688). Risk of unauthorized operations or information disclosure.
|
| ROOT-APP-PYPI-CVE-2023-6022 |
|
Vulnerability in rootio-prefect (ROOT-APP-PYPI-CVE-2023-6022)
vulnerability in rootio-prefect (ROOT-APP-PYPI-CVE-2023-6022). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `2.10.4+root.io.2, 2.10.4+root.io.3, 2.11.5+root.io.2, 2.14.13+root.io.1, 2.11.5+root.io.3, 2.10.4+root.io.4, 2.14.13+root.io.2` or later.
|
| ROOT-APP-PYPI-CVE-2024-8183 |
|
Vulnerability in rootio-prefect (ROOT-APP-PYPI-CVE-2024-8183)
vulnerability in rootio-prefect (ROOT-APP-PYPI-CVE-2024-8183). Confidential information can be exposed externally. Mitigation: upgrade to `2.10.4+root.io.1, 2.10.4+root.io.2, 2.10.4+root.io.3, 2.11.5+root.io.1, 2.11.5+root.io.2, 2.14.13+root.io.1, 2.11.5+root.io.3, 2.10.4+root.io.4, 2.14.13+root.io.2` or later.
|
| ROOT-APP-PYPI-CVE-2026-33236 |
|
Vulnerability in rootio-nltk (ROOT-APP-PYPI-CVE-2026-33236)
vulnerability in rootio-nltk (ROOT-APP-PYPI-CVE-2026-33236). Data can be tampered with by attackers. Mitigation: upgrade to `3.9.2+root.io.3, 3.9.2+root.io.4, 3.9.2+root.io.5, 3.9.2+root.io.6` or later.
|
| ROOT-APP-PYPI-CVE-2026-33230 |
|
Vulnerability in rootio-nltk (ROOT-APP-PYPI-CVE-2026-33230)
vulnerability in rootio-nltk (ROOT-APP-PYPI-CVE-2026-33230). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `3.9.2+root.io.2, 3.9.2+root.io.3, 3.9.2+root.io.4, 3.9.2+root.io.5, 3.9.2+root.io.6` or later.
|
| ROOT-APP-PYPI-CVE-2026-33231 |
|
Vulnerability in rootio-nltk (ROOT-APP-PYPI-CVE-2026-33231)
vulnerability in rootio-nltk (ROOT-APP-PYPI-CVE-2026-33231). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `3.9.2+root.io.4, 3.9.2+root.io.5, 3.9.2+root.io.6` or later.
|
| ROOT-APP-PYPI-CVE-2025-14009 |
|
Vulnerability in rootio-nltk (ROOT-APP-PYPI-CVE-2025-14009)
vulnerability in rootio-nltk (ROOT-APP-PYPI-CVE-2025-14009). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `3.9.2+root.io.1, 3.9.2+root.io.2, 3.9.2+root.io.3, 3.9.2+root.io.4, 3.9.2+root.io.5, 3.9.2+root.io.6` or later.
|
| ROOT-APP-PYPI-CVE-2026-0994 |
|
Vulnerability in rootio-protobuf (ROOT-APP-PYPI-CVE-2026-0994)
vulnerability in rootio-protobuf (ROOT-APP-PYPI-CVE-2026-0994). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `6.31.1+root.io.1, 3.20.0+root.io.2, 3.20.0+root.io.3, 4.24.1+root.io.2, 6.31.1+root.io.2, 4.25.9+root.io.1, 4.24.1+root.io.3, 4.25.9+root.io.2, 6.31.1+root.io.3, 4.24.4+root.io.1, 4.25.9+root.io.3, 4.25.9+root.io.4, 4.25.9+root.io.5, 4.25.9+root.io.6` or later.
|
| ROOT-APP-PYPI-CVE-2022-40899 |
|
Vulnerability in rootio-future (ROOT-APP-PYPI-CVE-2022-40899)
vulnerability in rootio-future (ROOT-APP-PYPI-CVE-2022-40899). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `0.18.2+root.io.1, 0.18.2+root.io.2, 0.18.2+root.io.3` or later.
|
| ROOT-APP-PYPI-CVE-2023-25692 |
|
Vulnerability in rootio-apache-airflow-providers-google (ROOT-APP-PYPI-CVE-2023-25692)
vulnerability in rootio-apache-airflow-providers-google (ROOT-APP-PYPI-CVE-2023-25692). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `8.1.0+root.io.1, 8.1.0+root.io.2, 8.1.0+root.io.3` or later.
|
| ROOT-APP-PYPI-CVE-2023-25691 |
|
Vulnerability in rootio-apache-airflow-providers-google (ROOT-APP-PYPI-CVE-2023-25691)
vulnerability in rootio-apache-airflow-providers-google (ROOT-APP-PYPI-CVE-2023-25691). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `8.1.0+root.io.1, 8.1.0+root.io.2, 8.1.0+root.io.3` or later.
|
| ROOT-APP-PYPI-CVE-2023-47248 |
|
Vulnerability in rootio-pyarrow (ROOT-APP-PYPI-CVE-2023-47248)
vulnerability in rootio-pyarrow (ROOT-APP-PYPI-CVE-2023-47248). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `6.0.1+root.io.1, 6.0.1+root.io.2` or later.
|
| ROOT-APP-PYPI-CVE-2026-25645 |
|
Vulnerability in rootio-requests (ROOT-APP-PYPI-CVE-2026-25645)
vulnerability in rootio-requests (ROOT-APP-PYPI-CVE-2026-25645). Data can be tampered with by attackers. Mitigation: upgrade to `2.32.5+root.io.1, 2.32.3+root.io.2, 2.28.1+root.io.1, 2.28.2+root.io.1, 2.30.0+root.io.1, 2.29.0+root.io.1, 2.30.0+root.io.2, 2.32.0+root.io.1, 2.32.5+root.io.2, 2.32.0+root.io.2, 2.32.3+root.io.3, 2.32.2+root.io.1, 2.32.4+root.io.1, 2.31.0+root.io.2, 2.31.0+root.io.3, 2.32.2+root.io.2, 2.28.2+root.io.2, 2.31.0+root.io.4, 2.32.3+root.io.4, 2.30.0+root.io.3, 2.32.5+root.io.3, 2.29.0+root.io.2, 2.32.0+root.io.3, 2.32.4+root.io.2, 2.28.1+root.io.2` or later.
|
| ROOT-APP-PYPI-CVE-2024-47081 |
|
Vulnerability in rootio-requests (ROOT-APP-PYPI-CVE-2024-47081)
vulnerability in rootio-requests (ROOT-APP-PYPI-CVE-2024-47081). Confidential information can be exposed externally. Mitigation: upgrade to `2.25.1+root.io.4, 2.32.3+root.io.1, 2.31.0+root.io.1, 2.19.0+root.io.4, 2.32.3+root.io.2, 2.28.1+root.io.1, 2.28.2+root.io.1, 2.30.0+root.io.1, 2.29.0+root.io.1, 2.30.0+root.io.2, 2.32.0+root.io.1, 2.32.0+root.io.2, 2.32.3+root.io.3, 2.32.2+root.io.1, 2.31.0+root.io.2, 2.31.0+root.io.3, 2.32.2+root.io.2, 2.25.1+root.io.5, 2.28.2+root.io.2, 2.31.0+root.io.4, 2.32.3+root.io.4, 2.30.0+root.io.3, 2.29.0+root.io.2, 2.32.0+root.io.3, 2.28.1+root.io.2` or later.
|
| ROOT-APP-PYPI-CVE-2023-26302 |
|
Vulnerability in rootio-markdown_it_py (ROOT-APP-PYPI-CVE-2023-26302)
vulnerability in rootio-markdown_it_py (ROOT-APP-PYPI-CVE-2023-26302). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `2.1.0+root.io.2, 2.1.0+root.io.3, 2.1.0+root.io.4, 2.1.0+root.io.5` or later.
|
| ROOT-APP-PYPI-CVE-2023-26303 |
|
Vulnerability in rootio-markdown_it_py (ROOT-APP-PYPI-CVE-2023-26303)
vulnerability in rootio-markdown_it_py (ROOT-APP-PYPI-CVE-2023-26303). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `2.1.0+root.io.1, 2.1.0+root.io.2, 2.1.0+root.io.3, 2.1.0+root.io.4, 2.1.0+root.io.5` or later.
|
| ROOT-APP-PYPI-CVE-2026-21226 |
|
Vulnerability in rootio-azure-core (ROOT-APP-PYPI-CVE-2026-21226)
vulnerability in rootio-azure-core (ROOT-APP-PYPI-CVE-2026-21226). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `1.35.0+root.io.1, 1.35.0+root.io.2, 1.35.0+root.io.3` or later.
|
| ROOT-APP-PYPI-CVE-2026-33936 |
|
Vulnerability in rootio-ecdsa (ROOT-APP-PYPI-CVE-2026-33936)
vulnerability in rootio-ecdsa (ROOT-APP-PYPI-CVE-2026-33936). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `0.19.1+root.io.1, 0.19.1+root.io.2, 0.19.1+root.io.3` or later.
|
| ROOT-APP-PYPI-CVE-2026-27459 |
|
Vulnerability in rootio-pyOpenSSL (ROOT-APP-PYPI-CVE-2026-27459)
vulnerability in rootio-pyOpenSSL (ROOT-APP-PYPI-CVE-2026-27459). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `24.3.0+root.io.1, 24.3.0+root.io.2, 24.3.0+root.io.3` or later.
|
| CVE-2026-7635 |
|
Unsafe Deserialization in wordpress (CVE-2026-7635)
vulnerability in wordpress (CVE-2026-7635). Successful exploitation can lead to full system takeover. Exploitable via `User-Agent header`.
|
| CVE-2026-7619 |
|
SQL Injection in wordpress (CVE-2026-7619)
SQL injection in wordpress (CVE-2026-7619). Confidential information can be exposed externally.
|
| CVE-2026-7051 |
|
Vulnerability in wordpress (CVE-2026-7051)
vulnerability in wordpress (CVE-2026-7051). Risk of unauthorized operations or information disclosure.
|
| CVE-2026-6962 |
|
Cross-Site Scripting (XSS) in wordpress (CVE-2026-6962)
cross-site scripting in wordpress (CVE-2026-6962). Risk of unauthorized operations or information disclosure.
|
| CVE-2026-6828 |
|
Cross-Site Scripting (XSS) in wordpress (CVE-2026-6828)
cross-site scripting in wordpress (CVE-2026-6828). Risk of unauthorized operations or information disclosure.
|
| CVE-2025-9989 |
|
Cross-Site Scripting (XSS) in wordpress (CVE-2025-9989)
cross-site scripting in wordpress (CVE-2025-9989). Risk of unauthorized operations or information disclosure.
|
| CVE-2025-9988 |
|
Vulnerability in wordpress (CVE-2025-9988)
vulnerability in wordpress (CVE-2025-9988). Risk of unauthorized operations or information disclosure.
|
| CVE-2025-9987 |
|
Information Disclosure in wordpress (CVE-2025-9987)
vulnerability in wordpress (CVE-2025-9987). Risk of unauthorized operations or information disclosure.
|
| CVE-2025-14755 |
|
Vulnerability in wordpress (CVE-2025-14755)
vulnerability in wordpress (CVE-2025-14755). Risk of unauthorized operations or information disclosure.
|
| MAL-2026-3683 |
|
Vulnerability in @dropout-ai/runtime (MAL-2026-3683)
vulnerability in @dropout-ai/runtime (MAL-2026-3683). Risk of unauthorized operations or information disclosure.
|
| CVE-2026-8336 |
|
Use-After-Free in mongodb (CVE-2026-8336)
vulnerability in mongodb (CVE-2026-8336). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `8.2.9, 8.3.2` or later.
|
| CVE-2026-8202 |
|
Vulnerability in mongodb (CVE-2026-8202)
vulnerability in mongodb (CVE-2026-8202). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `7.0.34, 8.0.23, 8.2.9, 8.3.2` or later.
|
| CVE-2026-8201 |
|
Use-After-Free in mongodb (CVE-2026-8201)
vulnerability in mongodb (CVE-2026-8201). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `7.0.34, 8.0.23, 8.2.9, 8.3.2` or later.
|
| CVE-2026-8200 |
|
Vulnerability in mongodb (CVE-2026-8200)
vulnerability in mongodb (CVE-2026-8200). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `7.0.34, 8.0.23, 8.2.9, 8.3.2` or later.
|
| CVE-2026-8199 |
|
Vulnerability in mongodb (CVE-2026-8199)
vulnerability in mongodb (CVE-2026-8199). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `7.0.34, 8.0.23, 8.2.9, 8.3.2` or later.
|