Last scanned:
This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker reaching the proxy on port 4000 could bypass access checks through a malformed Host header (CVE-2026-48710) and reach protected management routes without valid credentials (CVE-2026-49468), potentially exposing data and the LiteLLM configuration. The image runs as root, which raises the damage an attacker could do after a bypass. Do not deploy this image until the litellm and starlette packages are upgraded to fixed versions and the image is rescanned.
Hardening plan for this image · 4 steps. The first closes 3 actively exploited CVEs.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-49468 | CRITICAL9.8 | litellm 1.83.7 fixed in 1.84.0 | 3.0% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-48710 | HIGH8.45 | starlette 0.49.1 fixed in 1.0.1 | 70.3% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2026-40217 | HIGH8 | litellm 1.83.7 fixed in 1.83.10 | 15.5% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-111497 | HIGH8 | libbrotlicommon1 1.2.0-r3 fixed in 1.2.0-r7 | 55.5% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2026-111497 | HIGH8 | libbrotlidec1 1.2.0-r3 fixed in 1.2.0-r7 | 55.5% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2026-111497 | HIGH8 | libbrotlienc1 1.2.0-r3 fixed in 1.2.0-r7 | 55.5% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2026-39892 | HIGH7.84 | cryptography 46.0.5 fixed in 46.0.7 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-12773 | HIGH7.84 | litellm 1.83.7 fixed in 1.84.0 | 1.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-48818 | HIGH7.5 | starlette 0.49.1 fixed in 1.1.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-54283 | HIGH7.5 | starlette 0.49.1 fixed in 1.3.1 | 0.5% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-63374 | HIGH7.4 | anyio 4.8.0 fixed in 4.14.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102268 | HIGH7.28 | PyJWT 2.12.0 fixed in 2.14.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102267 | HIGH7.28 | PyJWT 2.12.0 fixed in 2.14.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| GHSA-6q48-6c7w-9gw2 | HIGH7.28 | certifi 2026.2.25 fixed in 2026.10.18 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-112940 | HIGH7.1 | filelock 3.25.2 fixed in 4.2.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-47101 | HIGH7.04 | litellm 1.83.7 fixed in 1.83.14 | 1.2% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-47102 | HIGH7.04 | litellm 1.83.7 fixed in 1.83.10 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| GHSA-2g87-pp6c-29x5 | MEDIUM6.96 | aiohttp 3.13.5 fixed in 3.14.4 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-111943 | MEDIUM6.8 | ca-certificates-bundle 20251003-r4 fixed in 20260909-r3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49265 | MEDIUM6.8 | oauthlib 3.3.1 fixed in 4.0.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28684 | MEDIUM6.6 | python-dotenv 1.0.1 fixed in 1.2.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102275 | MEDIUM6.56 | PyJWT 2.12.0 fixed in 2.15.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59822 | MEDIUM6.56 | litellm 1.83.7 fixed in 1.84.0 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-4437 | MEDIUM6.5 | glibc 2.43-r3 fixed in 2.43-r4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM6.5 | glibc-locale-posix 2.43-r3 fixed in 2.43-r4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM6.5 | ld-linux 2.43-r3 fixed in 2.43-r4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM6.5 | libcrypt1 2.43-r3 fixed in 2.43-r4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48816 | MEDIUM6.5 | @sigstore/verify 3.1.0 fixed in 3.1.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-84377 | MEDIUM6.5 | litellm 1.83.7 fixed in 1.88.6, 1.89.7, 1.90.7, 1.91.5, 1.92.2, 1.93.2, 1.94.3, 1.95.1, 1.96.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-28387 | MEDIUM6.48 | libcrypto3 3.6.1-r4 fixed in 3.6.2-r0 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-28387 | MEDIUM6.48 | libssl3 3.6.1-r4 fixed in 3.6.2-r0 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-34181 | MEDIUM6.3 | libcrypto3 3.6.1-r4 fixed in 3.6.3-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM6.3 | libcrypto3 3.6.1-r4 fixed in 3.6.3-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM6.3 | libssl3 3.6.1-r4 fixed in 3.6.3-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM6.3 | libssl3 3.6.1-r4 fixed in 3.6.3-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-14546 | MEDIUM6.3 | fastapi-sso 0.16.0 fixed in 0.19.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59890 | MEDIUM6.1 | py3.13-setuptools 82.0.1-r0 fixed in 83.0.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-49264 | MEDIUM6.1 | oauthlib 3.3.1 fixed in 4.0.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45186 | MEDIUM6 | libexpat1 2.7.5-r1 fixed in 2.8.1-r0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-101917 | MEDIUM6 | PyJWT 2.12.0 fixed in 2.14.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-101918 | MEDIUM6 | PyJWT 2.12.0 fixed in 2.15.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102274 | MEDIUM6 | PyJWT 2.12.0 fixed in 2.14.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-111064 | MEDIUM6 | aiohttp 3.13.5 fixed in 3.14.4 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-111066 | MEDIUM6 | aiohttp 3.13.5 fixed in 3.14.4 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-69244 | MEDIUM6 | aiohttp 3.13.5 fixed in 3.14.3 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-47265 | MEDIUM6 | aiohttp 3.13.5 fixed in 3.14.0 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54273 | MEDIUM6 | aiohttp 3.13.5 fixed in 3.14.1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54274 | MEDIUM6 | aiohttp 3.13.5 fixed in 3.14.1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54277 | MEDIUM6 | aiohttp 3.13.5 fixed in 3.14.1 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54278 | MEDIUM6 | aiohttp 3.13.5 fixed in 3.14.1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-50269 | MEDIUM6 | aiohttp 3.13.5 fixed in 3.14.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54275 | MEDIUM6 | aiohttp 3.13.5 fixed in 3.14.1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54279 | MEDIUM6 | aiohttp 3.13.5 fixed in 3.14.1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54280 | MEDIUM6 | aiohttp 3.13.5 fixed in 3.14.1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-69249 | MEDIUM6 | cryptography 46.0.5 fixed in 49.0.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| GHSA-537c-gmf6-5ccf | MEDIUM6 | cryptography 46.0.5 fixed in 48.0.1 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-50271 | MEDIUM6 | ddtrace 2.19.0 fixed in 4.8.2 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102993 | MEDIUM6 | pypdf 6.9.2 fixed in 6.17.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102994 | MEDIUM6 | pypdf 6.9.2 fixed in 6.18.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102995 | MEDIUM6 | pypdf 6.9.2 fixed in 6.18.1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102996 | MEDIUM6 | pypdf 6.9.2 fixed in 6.18.1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102997 | MEDIUM6 | pypdf 6.9.2 fixed in 6.18.1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102998 | MEDIUM6 | pypdf 6.9.2 fixed in 6.19.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102999 | MEDIUM6 | pypdf 6.9.2 fixed in 6.19.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-103000 | MEDIUM6 | pypdf 6.9.2 fixed in 6.19.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59935 | MEDIUM6 | pypdf 6.9.2 fixed in 6.14.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59936 | MEDIUM6 | pypdf 6.9.2 fixed in 6.14.1 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59937 | MEDIUM6 | pypdf 6.9.2 fixed in 6.14.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102271 | MEDIUM5.92 | PyJWT 2.12.0 fixed in 2.14.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-48526 | MEDIUM5.92 | PyJWT 2.12.0 fixed in 2.13.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| GHSA-pxh4-856f-4h89 | MEDIUM5.92 | PyJWT 2.12.0 fixed in 2.14.0 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-69248 | MEDIUM5.92 | cryptography 46.0.5 fixed in 49.0.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6791 | MEDIUM5.9 | glibc 2.43-r3 fixed in 2.43-r10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | glibc-locale-posix 2.43-r3 fixed in 2.43-r10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | ld-linux 2.43-r3 fixed in 2.43-r10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libcrypt1 2.43-r3 fixed in 2.43-r10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | libcrypto3 3.6.1-r4 fixed in 3.6.2-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-35188 | MEDIUM5.9 | libcrypto3 3.6.1-r4 fixed in 3.6.3-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | libcrypto3 3.6.1-r4 fixed in 3.6.3-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42765 | MEDIUM5.9 | libcrypto3 3.6.1-r4 fixed in 3.6.3-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.9 | libcrypto3 3.6.1-r4 fixed in 3.6.3-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.9 | libcrypto3 3.6.1-r4 fixed in 3.6.3-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.9 | libcrypto3 3.6.1-r4 fixed in 3.6.3-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | libssl3 3.6.1-r4 fixed in 3.6.2-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-35188 | MEDIUM5.9 | libssl3 3.6.1-r4 fixed in 3.6.3-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | libssl3 3.6.1-r4 fixed in 3.6.3-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42765 | MEDIUM5.9 | libssl3 3.6.1-r4 fixed in 3.6.3-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.9 | libssl3 3.6.1-r4 fixed in 3.6.3-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.9 | libssl3 3.6.1-r4 fixed in 3.6.3-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.9 | libssl3 3.6.1-r4 fixed in 3.6.3-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-104844 | MEDIUM5.9 | postcss-selector-parser 7.1.1 fixed in 7.1.6, 6.1.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | MEDIUM5.88 | libcrypto3 3.6.1-r4 fixed in 3.6.2-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | MEDIUM5.88 | libssl3 3.6.1-r4 fixed in 3.6.2-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-112393 | MEDIUM5.88 | pillow 12.1.1 fixed in 13.0.0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-96639 | MEDIUM5.88 | pillow 12.1.1 fixed in 13.0.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-34993 | MEDIUM5.84 | aiohttp 3.13.5 fixed in 3.14.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-69243 | MEDIUM5.6 | aiohttp 3.13.5 fixed in 3.14.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-112398 | MEDIUM5.52 | pillow 12.1.1 fixed in 13.0.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-112403 | MEDIUM5.52 | pillow 12.1.1 fixed in 13.0.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-112900 | MEDIUM5.52 | pillow 12.1.1 fixed in 13.0.0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.52 | libexpat1 2.7.5-r1 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56403 | MEDIUM5.52 | libexpat1 2.7.5-r1 fixed in 2.8.2-r0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56404 | MEDIUM5.52 | libexpat1 2.7.5-r1 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56405 | MEDIUM5.52 | libexpat1 2.7.5-r1 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56406 | MEDIUM5.52 | libexpat1 2.7.5-r1 fixed in 2.8.2-r0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56407 | MEDIUM5.52 | libexpat1 2.7.5-r1 fixed in 2.8.2-r0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56408 | MEDIUM5.52 | libexpat1 2.7.5-r1 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56410 | MEDIUM5.52 | libexpat1 2.7.5-r1 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56411 | MEDIUM5.52 | libexpat1 2.7.5-r1 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| GHSA-jm82-fx9c-mx94 | MEDIUM5.52 | pypdf 6.9.2 fixed in 6.13.3 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-7383 | MEDIUM5.5 | libcrypto3 3.6.1-r4 fixed in 3.6.3-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM5.5 | libssl3 3.6.1-r4 fixed in 3.6.3-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-64847 | MEDIUM5.5 | anyio 4.8.0 fixed in 4.14.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-67221 | MEDIUM5.5 | orjson 3.10.15 fixed in 3.11.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | MEDIUM5.46 | libcrypto3 3.6.1-r4 fixed in 3.6.3-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | MEDIUM5.46 | libssl3 3.6.1-r4 fixed in 3.6.3-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-54058 | MEDIUM5.46 | pillow 12.1.1 fixed in 12.3.0 | 0.5% Theoretical Threat | Directly Exposed |
| GHSA-98x5-vq43-vc5p | MEDIUM5.4 | semantic-router 0.1.11 fixed in 0.1.15 | — | Directly Exposed |
| CVE-2026-58055 | MEDIUM5.4 | libnghttp2-14 1.68.1-r2 fixed in 1.70.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48758 | MEDIUM5.4 | @sigstore/core 3.1.0 fixed in 3.2.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48758 | MEDIUM5.4 | @sigstore/core 3.2.0 fixed in 3.2.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | glibc 2.43-r3 fixed in 2.43-r6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | glibc-locale-posix 2.43-r3 fixed in 2.43-r6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | ld-linux 2.43-r3 fixed in 2.43-r6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | libcrypt1 2.43-r3 fixed in 2.43-r6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM5.3 | libcrypto3 3.6.1-r4 fixed in 3.6.3-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42767 | MEDIUM5.3 | libcrypto3 3.6.1-r4 fixed in 3.6.3-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM5.3 | libssl3 3.6.1-r4 fixed in 3.6.3-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42767 | MEDIUM5.3 | libssl3 3.6.1-r4 fixed in 3.6.3-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-102598 | MEDIUM5.3 | Werkzeug 3.1.8 fixed in 3.1.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45409 | MEDIUM5.3 | idna 3.11 fixed in 3.15 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59823 | MEDIUM5.3 | litellm 1.83.7 fixed in 1.83.9 | 0.4% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-104874 | MEDIUM5.3 | multidict 6.7.1 fixed in 6.9.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-114603 | MEDIUM5.3 | opentelemetry-api 1.28.0 fixed in 1.45.1 | 0.5% Theoretical Threat | Directly Exposed |
| GHSA-4xgf-cpjx-pc3j | MEDIUM5.3 | pydantic-settings 2.13.1 fixed in 2.14.2 | — | Directly Exposed |
| CVE-2026-48817 | MEDIUM5.3 | starlette 0.49.1 fixed in 1.1.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-54282 | MEDIUM5.3 | starlette 0.49.1 fixed in 1.3.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-104851 | MEDIUM5.28 | fsspec 2026.3.0 fixed in 2026.6.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-112902 | MEDIUM5.28 | pillow 12.1.1 fixed in 13.0.0 | — | Directly Exposed |
| CVE-2026-56409 | MEDIUM5.2 | libexpat1 2.7.5-r1 fixed in 2.8.2-r0 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-103001 | MEDIUM5.2 | PyJWT 2.12.0 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-111748 | MEDIUM5.2 | aiohttp 3.13.5 fixed in 3.14.4 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-41312 | MEDIUM5.2 | pypdf 6.9.2 fixed in 6.10.2 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-41313 | MEDIUM5.2 | pypdf 6.9.2 fixed in 6.10.2 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-41314 | MEDIUM5.2 | pypdf 6.9.2 fixed in 6.10.2 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-69192 | MEDIUM5.16 | ip-address 10.1.0 fixed in 10.3.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | glibc 2.43-r3 fixed in 2.43-r7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | glibc 2.43-r3 fixed in 2.43-r7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | glibc-locale-posix 2.43-r3 fixed in 2.43-r7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | glibc-locale-posix 2.43-r3 fixed in 2.43-r7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | ld-linux 2.43-r3 fixed in 2.43-r7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | ld-linux 2.43-r3 fixed in 2.43-r7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libcrypt1 2.43-r3 fixed in 2.43-r7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libcrypt1 2.43-r3 fixed in 2.43-r7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libcrypto3 3.6.1-r4 fixed in 3.6.3-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libssl3 3.6.1-r4 fixed in 3.6.3-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-85091 | MEDIUM5 | zlib 1.3.2-r2 fixed in 1.3.2.1_rc20260601-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-112404 | MEDIUM4.92 | pillow 12.1.1 fixed in 13.0.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-112896 | MEDIUM4.92 | pillow 12.1.1 fixed in 13.0.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59197 | MEDIUM4.92 | pillow 12.1.1 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-112394 | MEDIUM4.92 | pillow 12.1.1 fixed in 13.0.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-112395 | MEDIUM4.92 | pillow 12.1.1 fixed in 13.0.0 | 0.5% Theoretical Threat | Directly Exposed |
| GHSA-c2m8-h5v5-343r | MEDIUM4.92 | tornado 6.5.5 fixed in 6.5.9 | — | Directly Exposed |
| CVE-2026-59819 | MEDIUM4.9 | litellm 1.83.7 fixed in 1.83.10 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-54276 | MEDIUM4.88 | aiohttp 3.13.5 fixed in 3.14.1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-45447 | MEDIUM4.86 | libcrypto3 3.6.1-r4 fixed in 3.6.3-r0 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | libssl3 3.6.1-r4 fixed in 3.6.3-r0 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-6100 | MEDIUM4.86 | python-3.13 3.13.13-r1 fixed in 3.13.13-r2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM4.86 | python-3.13-base 3.13.13-r1 fixed in 3.13.13-r2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-59950 | MEDIUM4.86 | mcp 1.26.0 fixed in 1.28.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-96778 | MEDIUM4.86 | pillow 12.1.1 fixed in 13.0.0 | 0.5% Theoretical Threat | Directly Exposed |
| GHSA-78g4-xqwv-q3g8 | MEDIUM4.86 | pillow 12.1.1 fixed in 13.0.0 | — | Directly Exposed |
| CVE-2026-97687 | MEDIUM4.86 | urllib3 2.6.3 fixed in 2.8.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM4.72 | libexpat1 2.7.5-r1 fixed in 2.8.2-r0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56412 | MEDIUM4.72 | libexpat1 2.7.5-r1 fixed in 2.8.2-r0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-69247 | MEDIUM4.72 | cryptography 46.0.5 fixed in 50.0.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42311 | MEDIUM4.68 | pillow 12.1.1 fixed in 12.2.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-49853 | MEDIUM4.62 | tornado 6.5.5 fixed in 6.5.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52870 | MEDIUM4.56 | mcp 1.26.0 fixed in 1.27.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | libcrypto3 3.6.1-r4 fixed in 3.6.3-r5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-28386 | MEDIUM4.5 | libcrypto3 3.6.1-r4 fixed in 3.6.2-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM4.5 | libcrypto3 3.6.1-r4 fixed in 3.6.2-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM4.5 | libcrypto3 3.6.1-r4 fixed in 3.6.2-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM4.5 | libcrypto3 3.6.1-r4 fixed in 3.6.2-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-54876 | MEDIUM4.5 | libcrypto3 3.6.1-r4 fixed in 3.6.3-r4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34183 | MEDIUM4.5 | libcrypto3 3.6.1-r4 fixed in 3.6.3-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | libssl3 3.6.1-r4 fixed in 3.6.3-r5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-28386 | MEDIUM4.5 | libssl3 3.6.1-r4 fixed in 3.6.2-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM4.5 | libssl3 3.6.1-r4 fixed in 3.6.2-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM4.5 | libssl3 3.6.1-r4 fixed in 3.6.2-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM4.5 | libssl3 3.6.1-r4 fixed in 3.6.2-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-54876 | MEDIUM4.5 | libssl3 3.6.1-r4 fixed in 3.6.3-r4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34183 | MEDIUM4.5 | libssl3 3.6.1-r4 fixed in 3.6.3-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | openssl 3.6.2-r2 fixed in 3.6.3-r5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-54876 | MEDIUM4.5 | openssl 3.6.2-r2 fixed in 3.6.3-r4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34183 | MEDIUM4.5 | openssl 3.6.2-r2 fixed in 3.6.3-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-44432 | MEDIUM4.5 | py3-pip-wheel 26.0.1-r2 fixed in 26.1.2-r1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-97689 | MEDIUM4.5 | py3-pip-wheel 26.0.1-r2 fixed in 26.2.1-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44432 | MEDIUM4.5 | py3.13-pip 26.0.1-r2 fixed in 26.1.2-r1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-97689 | MEDIUM4.5 | py3.13-pip 26.0.1-r2 fixed in 26.2.1-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44432 | MEDIUM4.5 | py3.13-pip-base 26.0.1-r2 fixed in 26.1.2-r1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-97689 | MEDIUM4.5 | py3.13-pip-base 26.0.1-r2 fixed in 26.2.1-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM4.5 | python-3.13 3.13.13-r1 fixed in 3.13.14-r3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM4.5 | python-3.13 3.13.13-r1 fixed in 3.13.14-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM4.5 | python-3.13-base 3.13.13-r1 fixed in 3.13.14-r3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM4.5 | python-3.13-base 3.13.13-r1 fixed in 3.13.14-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-102276 | MEDIUM4.5 | brace-expansion 5.0.4 fixed in 5.0.10, 3.0.7, 2.1.5, 1.1.19 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-102278 | MEDIUM4.5 | brace-expansion 5.0.4 fixed in 5.0.11, 3.0.8, 2.1.6, 1.1.20 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-14257 | MEDIUM4.5 | brace-expansion 5.0.4 fixed in 5.0.8, 3.0.3, 2.1.3, 1.1.17 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-69152 | MEDIUM4.5 | brace-expansion 5.0.4 fixed in 1.1.18, 2.1.4, 3.0.6, 5.0.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33750 | MEDIUM4.5 | brace-expansion 5.0.4 fixed in 5.0.5, 3.0.2, 2.0.3, 1.1.13 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45149 | MEDIUM4.5 | brace-expansion 5.0.4 fixed in 5.0.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102276 | MEDIUM4.5 | brace-expansion 5.0.5 fixed in 5.0.10, 3.0.7, 2.1.5, 1.1.19 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-102278 | MEDIUM4.5 | brace-expansion 5.0.5 fixed in 5.0.11, 3.0.8, 2.1.6, 1.1.20 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-14257 | MEDIUM4.5 | brace-expansion 5.0.5 fixed in 5.0.8, 3.0.3, 2.1.3, 1.1.17 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-69152 | MEDIUM4.5 | brace-expansion 5.0.5 fixed in 1.1.18, 2.1.4, 3.0.6, 5.0.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45149 | MEDIUM4.5 | brace-expansion 5.0.5 fixed in 5.0.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93748 | MEDIUM4.5 | http-cache-semantics 4.2.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-9496 | MEDIUM4.5 | pacote 21.0.4 fixed in 21.5.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9496 | MEDIUM4.5 | pacote 21.5.0 fixed in 21.5.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-33671 | MEDIUM4.5 | picomatch 4.0.3 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48815 | MEDIUM4.5 | sigstore 4.1.0 fixed in 4.1.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59873 | MEDIUM4.5 | tar 7.5.11 fixed in 7.5.19 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-59874 | MEDIUM4.5 | tar 7.5.11 fixed in 7.5.18 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-73566 | MEDIUM4.5 | tar 7.5.11 fixed in 7.5.21 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59951 | MEDIUM4.5 | mcp 1.26.0 fixed in 1.30.0, 2.2.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-112390 | MEDIUM4.5 | pillow 12.1.1 fixed in 13.0.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-112392 | MEDIUM4.5 | pillow 12.1.1 fixed in 13.0.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-112397 | MEDIUM4.5 | pillow 12.1.1 fixed in 13.0.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-112399 | MEDIUM4.5 | pillow 12.1.1 fixed in 13.0.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-112400 | MEDIUM4.5 | pillow 12.1.1 fixed in 13.0.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-112402 | MEDIUM4.5 | pillow 12.1.1 fixed in 13.0.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-112405 | MEDIUM4.5 | pillow 12.1.1 fixed in 13.0.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-112406 | MEDIUM4.5 | pillow 12.1.1 fixed in 13.0.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-112892 | MEDIUM4.5 | pillow 12.1.1 fixed in 13.0.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-112893 | MEDIUM4.5 | pillow 12.1.1 fixed in 13.0.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-112894 | MEDIUM4.5 | pillow 12.1.1 fixed in 13.0.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-112895 | MEDIUM4.5 | pillow 12.1.1 fixed in 13.0.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-112897 | MEDIUM4.5 | pillow 12.1.1 fixed in 13.0.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40192 | MEDIUM4.5 | pillow 12.1.1 fixed in 12.2.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-54059 | MEDIUM4.5 | pillow 12.1.1 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54060 | MEDIUM4.5 | pillow 12.1.1 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-55379 | MEDIUM4.5 | pillow 12.1.1 fixed in 12.3.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-55380 | MEDIUM4.5 | pillow 12.1.1 fixed in 12.3.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59199 | MEDIUM4.5 | pillow 12.1.1 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59200 | MEDIUM4.5 | pillow 12.1.1 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59204 | MEDIUM4.5 | pillow 12.1.1 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59205 | MEDIUM4.5 | pillow 12.1.1 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-96640 | MEDIUM4.5 | pillow 12.1.1 fixed in 13.0.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-96643 | MEDIUM4.5 | pillow 12.1.1 fixed in 13.0.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-112391 | MEDIUM4.5 | pillow 12.1.1 fixed in 13.0.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-112396 | MEDIUM4.5 | pillow 12.1.1 fixed in 13.0.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-59198 | MEDIUM4.5 | pillow 12.1.1 fixed in 12.3.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59203 | MEDIUM4.5 | pillow 12.1.1 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59884 | MEDIUM4.5 | pyasn1 0.6.3 fixed in 0.6.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-59885 | MEDIUM4.5 | pyasn1 0.6.3 fixed in 0.6.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-59886 | MEDIUM4.5 | pyasn1 0.6.3 fixed in 0.6.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-24486 | MEDIUM4.5 | python-multipart 0.0.20 fixed in 0.0.22 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42561 | MEDIUM4.5 | python-multipart 0.0.20 fixed in 0.0.27 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-53539 | MEDIUM4.5 | python-multipart 0.0.20 fixed in 0.0.30 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-49855 | MEDIUM4.5 | tornado 6.5.5 fixed in 6.5.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-82397 | MEDIUM4.5 | tornado 6.5.5 fixed in 6.5.8 | 0.3% Theoretical Threat | Directly Exposed |
| GHSA-chx6-46f5-w4vp | MEDIUM4.5 | tornado 6.5.5 fixed in 6.5.9 | — | Directly Exposed |
| CVE-2026-44432 | MEDIUM4.5 | urllib3 2.6.3 fixed in 2.7.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-97689 | MEDIUM4.5 | urllib3 2.6.3 fixed in 2.8.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM4.44 | libcrypto3 3.6.1-r4 fixed in 3.6.3-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34182 | MEDIUM4.44 | libssl3 3.6.1-r4 fixed in 3.6.3-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-115572 | MEDIUM4.4 | pypdf 6.9.2 fixed in 6.21.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-115580 | MEDIUM4.4 | pypdf 6.9.2 fixed in 6.21.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-115585 | MEDIUM4.4 | pypdf 6.9.2 fixed in 6.21.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113789 | MEDIUM4.4 | pypdf 6.9.2 fixed in 6.21.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113790 | MEDIUM4.4 | pypdf 6.9.2 fixed in 6.21.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113791 | MEDIUM4.4 | pypdf 6.9.2 fixed in 6.21.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113792 | MEDIUM4.4 | pypdf 6.9.2 fixed in 6.20.1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113793 | MEDIUM4.4 | pypdf 6.9.2 fixed in 6.20.1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113794 | MEDIUM4.4 | pypdf 6.9.2 fixed in 6.20.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113795 | MEDIUM4.4 | pypdf 6.9.2 fixed in 6.20.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-48155 | MEDIUM4.4 | pypdf 6.9.2 fixed in 6.12.0 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-48735 | MEDIUM4.4 | pypdf 6.9.2 fixed in 6.12.1 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-49461 | MEDIUM4.4 | pypdf 6.9.2 fixed in 6.12.2 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54530 | MEDIUM4.4 | pypdf 6.9.2 fixed in 6.13.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54531 | MEDIUM4.4 | pypdf 6.9.2 fixed in 6.13.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54651 | MEDIUM4.4 | pypdf 6.9.2 fixed in 6.13.1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-84309 | MEDIUM4.4 | pypdf 6.9.2 fixed in 6.16.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-11940 | MEDIUM4.38 | python-3.13 3.13.13-r1 fixed in 3.13.14-r2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM4.38 | python-3.13-base 3.13.13-r1 fixed in 3.13.14-r2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-102269 | MEDIUM4.32 | PyJWT 2.12.0 fixed in 2.14.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-48523 | MEDIUM4.32 | PyJWT 2.12.0 fixed in 2.13.0 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-9358 | MEDIUM4.3 | postcss-selector-parser 7.1.1 fixed in 6.1.3, 7.1.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4786 | MEDIUM4.26 | python-3.13 3.13.13-r1 fixed in 3.13.13-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-82049 | MEDIUM4.26 | python-3.13 3.13.13-r1 fixed in 3.13.15_git20260912-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM4.26 | python-3.13 3.13.13-r1 fixed in 3.13.15-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4786 | MEDIUM4.26 | python-3.13-base 3.13.13-r1 fixed in 3.13.13-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-82049 | MEDIUM4.26 | python-3.13-base 3.13.13-r1 fixed in 3.13.15_git20260912-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM4.26 | python-3.13-base 3.13.13-r1 fixed in 3.13.15-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52869 | MEDIUM4.26 | mcp 1.26.0 fixed in 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-96644 | MEDIUM4.26 | pillow 12.1.1 fixed in 13.0.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48525 | MEDIUM4.24 | PyJWT 2.12.0 fixed in 2.13.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-111065 | MEDIUM4.24 | aiohttp 3.13.5 fixed in 3.14.4 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59881 | MEDIUM4.24 | aiohttp 3.13.5 fixed in 3.14.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-34073 | MEDIUM4.24 | cryptography 46.0.5 fixed in 46.0.6 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-40260 | MEDIUM4.24 | pypdf 6.9.2 fixed in 6.10.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-41168 | MEDIUM4.24 | pypdf 6.9.2 fixed in 6.10.1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59938 | MEDIUM4.24 | pypdf 6.9.2 fixed in 6.14.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-82398 | MEDIUM4.24 | pypdf 6.9.2 fixed in 6.15.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-112899 | MEDIUM4.14 | pillow 12.1.1 fixed in 13.0.0 | — | Directly Exposed |
| GHSA-8423-8fgw-73vq | MEDIUM4.14 | tornado 6.5.5 fixed in 6.5.8 | — | Directly Exposed |
| CVE-2026-4438 | MEDIUM4 | glibc 2.43-r3 fixed in 2.43-r4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | MEDIUM4 | glibc-locale-posix 2.43-r3 fixed in 2.43-r4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | MEDIUM4 | ld-linux 2.43-r3 fixed in 2.43-r4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | MEDIUM4 | libcrypt1 2.43-r3 fixed in 2.43-r4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-39810 | LOW3.98 | busybox 1.37.0-r57 fixed in 1.37.0-r58 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-102270 | LOW3.92 | PyJWT 2.12.0 fixed in 2.14.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-38752 | LOW3.9 | busybox 1.37.0-r57 fixed in 1.38.0-r1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.9 | python-3.13 3.13.13-r1 fixed in 3.13.14-r2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-15310 | LOW3.9 | python-3.13 3.13.13-r1 fixed in 3.13.16_git20261002-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-17084 | LOW3.9 | python-3.13 3.13.13-r1 fixed in 3.13.15-r6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | LOW3.9 | python-3.13 3.13.13-r1 fixed in 3.13.14-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | LOW3.9 | python-3.13-base 3.13.13-r1 fixed in 3.13.14-r2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-15310 | LOW3.9 | python-3.13-base 3.13.13-r1 fixed in 3.13.16_git20261002-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-17084 | LOW3.9 | python-3.13-base 3.13.13-r1 fixed in 3.13.15-r6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | LOW3.9 | python-3.13-base 3.13.13-r1 fixed in 3.13.14-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-96637 | LOW3.9 | pillow 12.1.1 fixed in 13.0.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-96642 | LOW3.9 | pillow 12.1.1 fixed in 13.0.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-96636 | LOW3.9 | pillow 12.1.1 fixed in 13.0.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-96638 | LOW3.9 | pillow 12.1.1 fixed in 13.0.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-96641 | LOW3.9 | pillow 12.1.1 fixed in 13.0.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-111750 | LOW3.84 | aiohttp 3.13.5 fixed in 3.14.4 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-34181 | LOW3.78 | openssl 3.6.2-r2 fixed in 3.6.3-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42768 | LOW3.78 | openssl 3.6.2-r2 fixed in 3.6.3-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW3.7 | libcrypto3 3.6.1-r4 fixed in 3.6.3-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.7 | libssl3 3.6.1-r4 fixed in 3.6.3-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | LOW3.66 | python-3.13 3.13.13-r1 fixed in 3.13.13-r3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | LOW3.66 | python-3.13-base 3.13.13-r1 fixed in 3.13.13-r3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42338 | LOW3.66 | ip-address 10.1.0 fixed in 10.1.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56131 | LOW3.6 | libexpat1 2.7.5-r1 fixed in 2.8.2-r0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-35188 | LOW3.54 | openssl 3.6.2-r2 fixed in 3.6.3-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42764 | LOW3.54 | openssl 3.6.2-r2 fixed in 3.6.3-r0 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42765 | LOW3.54 | openssl 3.6.2-r2 fixed in 3.6.3-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42769 | LOW3.54 | openssl 3.6.2-r2 fixed in 3.6.3-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.54 | openssl 3.6.2-r2 fixed in 3.6.3-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.54 | openssl 3.6.2-r2 fixed in 3.6.3-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-9669 | LOW3.54 | python-3.13 3.13.13-r1 fixed in 3.13.14-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | LOW3.54 | python-3.13-base 3.13.13-r1 fixed in 3.13.14-r0 | 0.4% Theoretical Threat | Directly Exposed |
| GHSA-pw6j-qg29-8w7f | LOW3.54 | tornado 6.5.5 fixed in 6.5.7 | — | Directly Exposed |
| CVE-2026-6357 | LOW3.48 | py3-pip-wheel 26.0.1-r2 fixed in 26.1.1-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6357 | LOW3.48 | py3.13-pip 26.0.1-r2 fixed in 26.1.1-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6357 | LOW3.48 | py3.13-pip-base 26.0.1-r2 fixed in 26.1.1-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-87910 | LOW3.42 | python-3.13 3.13.13-r1 fixed in 3.13.16_git20261002-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-87910 | LOW3.42 | python-3.13-base 3.13.13-r1 fixed in 3.13.16_git20261002-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-48522 | LOW3.36 | PyJWT 2.12.0 fixed in 2.13.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-111749 | LOW3.36 | aiohttp 3.13.5 fixed in 3.14.4 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-38755 | LOW3.3 | busybox 1.37.0-r57 fixed in 1.38.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW3.3 | openssl 3.6.2-r2 fixed in 3.6.3-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-25645 | LOW3.3 | py3-pip-wheel 26.0.1-r2 fixed in 26.1.1-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25645 | LOW3.3 | py3.13-pip 26.0.1-r2 fixed in 26.1.1-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25645 | LOW3.3 | py3.13-pip-base 26.0.1-r2 fixed in 26.1.1-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | LOW3.3 | python-3.13 3.13.13-r1 fixed in 3.13.14-r2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | LOW3.3 | python-3.13-base 3.13.13-r1 fixed in 3.13.14-r2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53655 | LOW3.3 | tar 7.5.11 fixed in 7.5.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42308 | LOW3.3 | pillow 12.1.1 fixed in 12.2.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42309 | LOW3.3 | pillow 12.1.1 fixed in 12.2.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42310 | LOW3.3 | pillow 12.1.1 fixed in 12.2.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-112913 | LOW3.3 | filelock 3.25.2 fixed in 4.2.1 | — | Directly Exposed |
| CVE-2026-45445 | LOW3.28 | openssl 3.6.2-r2 fixed in 3.6.3-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW3.18 | openssl 3.6.2-r2 fixed in 3.6.3-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42767 | LOW3.18 | openssl 3.6.2-r2 fixed in 3.6.3-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-44431 | LOW3.18 | py3-pip-wheel 26.0.1-r2 fixed in 26.1.2-r1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45409 | LOW3.18 | py3-pip-wheel 26.0.1-r2 fixed in 26.1.2-r1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-97688 | LOW3.18 | py3-pip-wheel 26.0.1-r2 fixed in 26.2.1-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44431 | LOW3.18 | py3.13-pip 26.0.1-r2 fixed in 26.1.2-r1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45409 | LOW3.18 | py3.13-pip 26.0.1-r2 fixed in 26.1.2-r1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-97688 | LOW3.18 | py3.13-pip 26.0.1-r2 fixed in 26.2.1-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44431 | LOW3.18 | py3.13-pip-base 26.0.1-r2 fixed in 26.1.2-r1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45409 | LOW3.18 | py3.13-pip-base 26.0.1-r2 fixed in 26.1.2-r1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-97688 | LOW3.18 | py3.13-pip-base 26.0.1-r2 fixed in 26.2.1-r2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8328 | LOW3.18 | python-3.13 3.13.13-r1 fixed in 3.13.13-r6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | LOW3.18 | python-3.13 3.13.13-r1 fixed in 3.13.14-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-15806 | LOW3.18 | python-3.13 3.13.13-r1 fixed in 3.13.15-r5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-19672 | LOW3.18 | python-3.13 3.13.13-r1 fixed in 3.13.16_git20261002-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | LOW3.18 | python-3.13 3.13.13-r1 fixed in 3.13.14-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | LOW3.18 | python-3.13 3.13.13-r1 fixed in 3.13.14-r2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8328 | LOW3.18 | python-3.13-base 3.13.13-r1 fixed in 3.13.13-r6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | LOW3.18 | python-3.13-base 3.13.13-r1 fixed in 3.13.14-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-15806 | LOW3.18 | python-3.13-base 3.13.13-r1 fixed in 3.13.15-r5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-19672 | LOW3.18 | python-3.13-base 3.13.13-r1 fixed in 3.13.16_git20261002-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | LOW3.18 | python-3.13-base 3.13.13-r1 fixed in 3.13.14-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | LOW3.18 | python-3.13-base 3.13.13-r1 fixed in 3.13.14-r2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-13149 | LOW3.18 | brace-expansion 5.0.4 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102277 | LOW3.18 | brace-expansion 5.0.4 fixed in 5.0.12, 3.0.9, 2.1.7, 1.1.21 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13149 | LOW3.18 | brace-expansion 5.0.5 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102277 | LOW3.18 | brace-expansion 5.0.5 fixed in 5.0.12, 3.0.9, 2.1.7, 1.1.21 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-101911 | LOW3.18 | ip-address 10.1.0 fixed in 10.7.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-101912 | LOW3.18 | ip-address 10.1.0 fixed in 10.7.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-101913 | LOW3.18 | ip-address 10.1.0 fixed in 10.5.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-111997 | LOW3.18 | ip-address 10.1.0 fixed in 10.7.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-33672 | LOW3.18 | picomatch 4.0.3 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59875 | LOW3.18 | tar 7.5.11 fixed in 7.5.17 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-112401 | LOW3.18 | pillow 12.1.1 fixed in 13.0.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-112891 | LOW3.18 | pillow 12.1.1 fixed in 13.0.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-112898 | LOW3.18 | pillow 12.1.1 fixed in 13.0.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-112901 | LOW3.18 | pillow 12.1.1 fixed in 13.0.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40347 | LOW3.18 | python-multipart 0.0.20 fixed in 0.0.26 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53537 | LOW3.18 | python-multipart 0.0.20 fixed in 0.0.30 | 0.3% Theoretical Threat | Directly Exposed |
| GHSA-3hv7-mjh2-fv65 | LOW3.18 | tornado 6.5.5 fixed in 6.5.9 | — | Directly Exposed |
| CVE-2026-44431 | LOW3.18 | urllib3 2.6.3 fixed in 2.7.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97688 | LOW3.18 | urllib3 2.6.3 fixed in 2.8.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-50181 | LOW3.11 | py3-pip-wheel 26.0.1-r2 fixed in 26.1.1-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-50181 | LOW3.11 | py3.13-pip 26.0.1-r2 fixed in 26.1.1-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-50181 | LOW3.11 | py3.13-pip-base 26.0.1-r2 fixed in 26.1.1-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | LOW3 | openssl 3.6.2-r2 fixed in 3.6.3-r0 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3219 | LOW3 | py3-pip-wheel 26.0.1-r2 fixed in 26.1.1-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3219 | LOW3 | py3.13-pip 26.0.1-r2 fixed in 26.1.1-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3219 | LOW3 | py3.13-pip-base 26.0.1-r2 fixed in 26.1.1-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW2.96 | libexpat1 2.7.5-r1 fixed in 2.8.0-r0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-48524 | LOW2.96 | PyJWT 2.12.0 fixed in 2.13.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-111063 | LOW2.96 | aiohttp 3.13.5 fixed in 3.14.4 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-45447 | LOW2.92 | openssl 3.6.2-r2 fixed in 3.6.3-r0 | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-97687 | LOW2.92 | py3-pip-wheel 26.0.1-r2 fixed in 26.2.1-r2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-97687 | LOW2.92 | py3.13-pip 26.0.1-r2 fixed in 26.2.1-r2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-97687 | LOW2.92 | py3.13-pip-base 26.0.1-r2 fixed in 26.2.1-r2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-38754 | LOW2.7 | busybox 1.37.0-r57 fixed in 1.38.0-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-38753 | LOW2.7 | busybox 1.37.0-r57 fixed in 1.38.0-r0 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66418 | LOW2.7 | py3-pip-wheel 26.0.1-r2 fixed in 26.1.1-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-66471 | LOW2.7 | py3-pip-wheel 26.0.1-r2 fixed in 26.1.1-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-21441 | LOW2.7 | py3-pip-wheel 26.0.1-r2 fixed in 26.1.1-r0 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-66418 | LOW2.7 | py3.13-pip 26.0.1-r2 fixed in 26.1.1-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-66471 | LOW2.7 | py3.13-pip 26.0.1-r2 fixed in 26.1.1-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-21441 | LOW2.7 | py3.13-pip 26.0.1-r2 fixed in 26.1.1-r0 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-66418 | LOW2.7 | py3.13-pip-base 26.0.1-r2 fixed in 26.1.1-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-66471 | LOW2.7 | py3.13-pip-base 26.0.1-r2 fixed in 26.1.1-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-21441 | LOW2.7 | py3.13-pip-base 26.0.1-r2 fixed in 26.1.1-r0 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-59871 | LOW2.7 | tar 7.5.11 fixed in 7.5.18 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.7 | python-3.13 3.13.13-r1 fixed in 3.13.13-r2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW2.7 | python-3.13-base 3.13.13-r1 fixed in 3.13.13-r2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-55798 | LOW2.7 | pillow 12.1.1 fixed in 12.3.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | LOW2.66 | openssl 3.6.2-r2 fixed in 3.6.3-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-48156 | LOW2.64 | pypdf 6.9.2 fixed in 6.12.0 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-49460 | LOW2.64 | pypdf 6.9.2 fixed in 6.12.2 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-71852 | LOW2.64 | pypdf 6.9.2 fixed in 6.15.0 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-71870 | LOW2.64 | pypdf 6.9.2 fixed in 6.15.0 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-84310 | LOW2.64 | pypdf 6.9.2 fixed in 6.16.1 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-84311 | LOW2.64 | pypdf 6.9.2 fixed in 6.16.1 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113786 | LOW2.64 | pypdf 6.9.2 fixed in 6.21.1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-26157 | LOW2.52 | busybox 1.37.0-r57 fixed in 1.37.0-r58 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-26158 | LOW2.52 | busybox 1.37.0-r57 fixed in 1.37.0-r58 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-112907 | LOW2.5 | filelock 3.25.2 fixed in 4.2.1 | — | Directly Exposed |
| CVE-2026-45446 | LOW2.22 | openssl 3.6.2-r2 fixed in 3.6.3-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-114501 | LOW2.22 | pillow 12.1.1 fixed in 13.0.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53538 | LOW2.22 | python-multipart 0.0.20 fixed in 0.0.30 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53540 | LOW2.22 | python-multipart 0.0.20 fixed in 0.0.31 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49854 | LOW2.22 | tornado 6.5.5 fixed in 6.5.6 | 0.4% Theoretical Threat | Directly Exposed |
| GHSA-wwv5-g3v4-889x | LOW1.38 | tornado 6.5.5 fixed in 6.5.8 | — | Directly Exposed |
| CVE-2026-6879 | LOW1.32 | python-3.13 3.13.13-r1 fixed in 3.13.15-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6879 | LOW1.32 | python-3.13-base 3.13.13-r1 fixed in 3.13.15-r0 | 0.4% Theoretical Threat | Directly Exposed |
Want to check another image? Run a full scan with the Docker Security Scanner.