Last scanned:
··This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker who exploited the lodash or protobufjs flaws could run code inside the Node process, which runs as root in this container, and could then control the monitoring service. Both flaws need conditions the image is not known to meet, so their practical risk is lower than their severity suggests. Note: CVE-2026-110922 only applies if a real-browser monitor is enabled. Remediating the flagged dependencies and reviewing whether the browser-based monitor is needed would reduce exposure.
Hardening plan for this image · 5 steps
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-4800 | HIGH7.84 | lodash 4.17.23 fixed in 4.18.0 | 2.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-41242 | HIGH7.84 | protobufjs 7.2.6 fixed in 8.0.1, 7.5.5 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-110922 | HIGH7.68 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113341 | HIGH7.68 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-110922 | HIGH7.68 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113341 | HIGH7.68 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-111181 | HIGH7.5 | body-parser 1.20.8 fixed in 2.4.0, 1.20.9 | 0.4% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-48779 | HIGH7.5 | ws 8.19.0 fixed in 5.2.5, 6.2.4, 7.5.11, 8.21.0 | 1.4% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-110913 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-110917 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-110918 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-110919 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-110920 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-110921 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-112993 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113006 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113017 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113025 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113030 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113033 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113037 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113039 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113043 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113057 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113068 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113073 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113074 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113081 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113082 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113091 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113113 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113115 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113117 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113128 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113130 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113134 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113137 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113143 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113161 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113165 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113207 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113210 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113216 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113217 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113233 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113234 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113242 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113252 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113264 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113266 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113273 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113274 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113278 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113285 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113293 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113295 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113305 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113314 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113315 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113319 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113321 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113323 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113324 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113334 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113344 | HIGH7.04 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-110913 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-110917 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-110918 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-110919 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-110920 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-110921 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-112993 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113006 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113017 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113025 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113030 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113033 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113037 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113039 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113043 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113057 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113068 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113073 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113074 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113081 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113082 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113091 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113113 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113115 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113117 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113128 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113130 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113134 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113137 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113143 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113161 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113165 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113207 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113210 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113216 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113217 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113233 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113234 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113242 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113252 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113264 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113266 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113273 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113274 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113278 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113285 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113293 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113295 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113305 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113314 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113315 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113319 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113321 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113323 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113324 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113334 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113344 | HIGH7.04 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-44293 | HIGH7.04 | protobufjs 7.2.6 fixed in 7.5.6, 8.0.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-61556 | MEDIUM6.96 | liquidjs 10.26.0 fixed in 10.27.1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-55575 | MEDIUM6.56 | liquidjs 10.26.0 fixed in 10.27.1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| GHSA-3f6p-5ww8-9rcr | MEDIUM6.56 | mysql2 3.11.5 fixed in 3.22.0 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2025-68468 | MEDIUM6.5 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM6.5 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM6.5 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-68468 | MEDIUM6.5 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM6.5 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM6.5 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-68468 | MEDIUM6.5 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM6.5 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM6.5 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM6.5 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM6.5 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM6.5 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM6.5 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM6.5 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM6.5 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-85231 | MEDIUM6.5 | libtirpc-common 1.3.3+ds-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85231 | MEDIUM6.5 | libtirpc3 1.3.3+ds-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93541 | MEDIUM6.5 | libxi6 2:1.8-1+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93542 | MEDIUM6.5 | libxi6 2:1.8-1+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93543 | MEDIUM6.5 | libxi6 2:1.8-1+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93544 | MEDIUM6.5 | libxi6 2:1.8-1+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93545 | MEDIUM6.5 | libxi6 2:1.8-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94281 | MEDIUM6.5 | libxi6 2:1.8-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44291 | MEDIUM6.48 | protobufjs 7.2.6 fixed in 7.5.6, 8.0.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54371 | MEDIUM6.3 | libattr1 1:2.5.1-4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-12345 | MEDIUM6.3 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-12345 | MEDIUM6.3 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM6.2 | libp11-kit0 0.24.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18938 | MEDIUM6.2 | libp11-kit0 0.24.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.16 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-95619 | MEDIUM6.16 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-95619 | MEDIUM6.16 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-90781 | MEDIUM6.1 | libasound2 1.2.8-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90781 | MEDIUM6.1 | libasound2-data 1.2.8-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18090 | MEDIUM6.1 | libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18090 | MEDIUM6.1 | libgdk-pixbuf2.0-common 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94282 | MEDIUM6.1 | libxi6 2:1.8-1+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-32681 | MEDIUM6.1 | python3-requests 2.28.1+dfsg-1 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-111497 | MEDIUM6 | libbrotli1 1.0.9-2+b6 fixed in 1.0.9-2+deb12u1 | 82.6% Actively Exploited | Directly Exposed |
| CVE-2026-109461 | MEDIUM6 | @azure/msal-node 5.6.0 fixed in 7.1.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-69222 | MEDIUM6 | liquidjs 10.26.0 fixed in 10.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-26996 | MEDIUM6 | minimatch 9.0.3 fixed in 10.2.1, 9.0.6, 8.0.5, 7.4.7, 6.2.1, 5.1.7, 4.2.4, 3.1.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-27903 | MEDIUM6 | minimatch 9.0.3 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-27904 | MEDIUM6 | minimatch 9.0.3 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.4 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-44289 | MEDIUM6 | protobufjs 7.2.6 fixed in 7.5.6, 8.0.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-44290 | MEDIUM6 | protobufjs 7.2.6 fixed in 7.5.6, 8.0.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-48712 | MEDIUM6 | protobufjs 7.2.6 fixed in 7.6.1, 8.4.1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-45740 | MEDIUM6 | protobufjs 7.2.6 fixed in 7.5.8, 8.2.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-45736 | MEDIUM6 | ws 8.19.0 fixed in 8.20.1 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-5435 | MEDIUM5.9 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-113351 | MEDIUM5.9 | libexpat1 2.5.0-1+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.9 | libssl3 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.9 | libssl3 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.9 | libssl3 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.19.0-2+deb12u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | nscd 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | nscd 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | nscd 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | nscd 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-45853 | MEDIUM5.88 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.6 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102010 | MEDIUM5.6 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102010 | MEDIUM5.6 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2023-5388 | MEDIUM5.52 | libnss3 2:3.87.1-1+deb12u4 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-7531 | MEDIUM5.52 | libnss3 2:3.87.1-1+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-39329 | MEDIUM5.52 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-96675 | MEDIUM5.5 | libasound2 1.2.8-1+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-96675 | MEDIUM5.5 | libasound2-data 1.2.8-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-59529 | MEDIUM5.5 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM5.5 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM5.5 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59529 | MEDIUM5.5 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM5.5 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM5.5 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59529 | MEDIUM5.5 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM5.5 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM5.5 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc6 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-111879 | MEDIUM5.5 | libdbi-perl 1.643-4+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM5.5 | libexpat1 2.5.0-1+deb12u5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95512 | MEDIUM5.5 | libfreetype6 2.12.1+dfsg-5+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM5.5 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM5.5 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libsystemd-shared 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libudev1 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4367 | MEDIUM5.5 | libxpm4 1:3.5.12-1.1+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94287 | MEDIUM5.5 | libxpm4 1:3.5.12-1.1+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | nscd 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25645 | MEDIUM5.5 | python3-requests 2.28.1+dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102267 | MEDIUM5.46 | python3-jwt 2.6.0-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102268 | MEDIUM5.46 | python3-jwt 2.6.0-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | MEDIUM5.4 | libnghttp2-14 1.52.0-1+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-16768 | MEDIUM5.3 | libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-16768 | MEDIUM5.3 | libgdk-pixbuf2.0-common 2.42.10+dfsg-1+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM5.3 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM5.3 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM5.3 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM5.3 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM5.3 | libssl3 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-85977 | MEDIUM5.3 | libtirpc-common 1.3.3+ds-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85977 | MEDIUM5.3 | libtirpc3 1.3.3+ds-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | nscd 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45409 | MEDIUM5.3 | python3-idna 3.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-47081 | MEDIUM5.3 | python3-requests 2.28.1+dfsg-1 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-82417 | MEDIUM5.3 | qs 6.14.2 fixed in 6.16.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8723 | MEDIUM5.3 | qs 6.14.2 fixed in 6.15.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-113011 | MEDIUM5.28 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-113011 | MEDIUM5.28 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85746 | MEDIUM5.28 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | MEDIUM5.28 | libsystemd-shared 252.39-1~deb12u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | MEDIUM5.28 | libsystemd0 252.39-1~deb12u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | MEDIUM5.28 | libudev1 252.39-1~deb12u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-85746 | MEDIUM5.28 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-85746 | MEDIUM5.28 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-85746 | MEDIUM5.28 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-85746 | MEDIUM5.28 | mariadb-server 1:10.11.19-0+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-85746 | MEDIUM5.28 | mariadb-server-core 1:10.11.19-0+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-110914 | MEDIUM5.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-110915 | MEDIUM5.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-110916 | MEDIUM5.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113106 | MEDIUM5.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113157 | MEDIUM5.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113200 | MEDIUM5.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113250 | MEDIUM5.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113340 | MEDIUM5.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-110914 | MEDIUM5.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-110915 | MEDIUM5.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-110916 | MEDIUM5.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113106 | MEDIUM5.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113157 | MEDIUM5.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113200 | MEDIUM5.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113250 | MEDIUM5.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113340 | MEDIUM5.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2011-3389 | MEDIUM5.07 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2023-32570 | MEDIUM5.02 | libdav1d6 1.0.0-2+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM5 | libbz2-1.0 1.0.8-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc-bin 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc6 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | nscd 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | nscd 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102275 | MEDIUM4.92 | python3-jwt 2.6.0-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-101909 | MEDIUM4.92 | axios 0.32.0 fixed in 0.34.0, 1.20.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc6 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | nscd 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-8458 | MEDIUM4.86 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8458 | MEDIUM4.86 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-97687 | MEDIUM4.86 | python3-urllib3 1.26.12-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libfdisk1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-106120 | MEDIUM4.8 | liquidjs 10.26.0 fixed in 10.27.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2024-35195 | MEDIUM4.76 | python3-requests 2.28.1+dfsg-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libfdisk1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| GHSA-rgwj-5xj2-c3m3 | MEDIUM4.72 | mysql2 3.11.5 fixed in 3.23.1 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-108518 | MEDIUM4.7 | libdbi-perl 1.643-4+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-81893 | MEDIUM4.7 | libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-81893 | MEDIUM4.7 | libgdk-pixbuf2.0-common 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libfdisk1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libfdisk1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11822 | MEDIUM4.68 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11824 | MEDIUM4.68 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11824 | MEDIUM4.68 | sqlite3 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-39328 | MEDIUM4.67 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7458 | MEDIUM4.64 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-7458 | MEDIUM4.64 | sqlite3 3.40.1-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM4.62 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM4.62 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM4.62 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM4.62 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM4.62 | mariadb-server 1:10.11.19-0+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM4.62 | mariadb-server-core 1:10.11.19-0+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-12064 | MEDIUM4.5 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6276 | MEDIUM4.5 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8927 | MEDIUM4.5 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8932 | MEDIUM4.5 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34980 | MEDIUM4.5 | libcups2 2.4.2-3+deb12u9 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-55453 | MEDIUM4.5 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-12064 | MEDIUM4.5 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6276 | MEDIUM4.5 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8927 | MEDIUM4.5 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8932 | MEDIUM4.5 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-2953 | MEDIUM4.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107815 | MEDIUM4.5 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9538 | MEDIUM4.5 | libperl5.36 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM4.5 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM4.5 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM4.5 | libsasl2-2 2.1.28+dfsg-10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM4.5 | libsasl2-modules-db 2.1.28+dfsg-10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52355 | MEDIUM4.5 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-36849 | MEDIUM4.5 | libtiff6 4.5.0-6+deb12u4 No fix yet | — | Directly Exposed |
| CVE-2026-88806 | MEDIUM4.5 | libx11-6 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | MEDIUM4.5 | libx11-data 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | MEDIUM4.5 | libx11-xcb1 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107815 | MEDIUM4.5 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107815 | MEDIUM4.5 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107815 | MEDIUM4.5 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107815 | MEDIUM4.5 | mariadb-server 1:10.11.19-0+deb12u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107815 | MEDIUM4.5 | mariadb-server-core 1:10.11.19-0+deb12u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-50782 | MEDIUM4.5 | python3-cryptography 38.0.4-3+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-69249 | MEDIUM4.5 | python3-cryptography 38.0.4-3+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-101917 | MEDIUM4.5 | python3-jwt 2.6.0-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-101918 | MEDIUM4.5 | python3-jwt 2.6.0-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102274 | MEDIUM4.5 | python3-jwt 2.6.0-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66471 | MEDIUM4.5 | python3-urllib3 1.26.12-1+deb12u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-97689 | MEDIUM4.5 | python3-urllib3 1.26.12-1+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48068 | MEDIUM4.5 | @grpc/grpc-js 1.8.22 fixed in 1.9.16, 1.10.12, 1.11.4, 1.12.7, 1.13.5, 1.14.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-48069 | MEDIUM4.5 | @grpc/grpc-js 1.8.22 fixed in 1.9.16, 1.10.12, 1.11.4, 1.12.7, 1.13.5, 1.14.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-67320 | MEDIUM4.5 | axios 0.32.0 fixed in 0.33.0, 1.18.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-67312 | MEDIUM4.5 | axios 0.32.0 fixed in 0.33.0, 1.18.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-67313 | MEDIUM4.5 | axios 0.32.0 fixed in 0.33.0, 1.18.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-67315 | MEDIUM4.5 | axios 0.32.0 fixed in 1.18.0, 0.33.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-67321 | MEDIUM4.5 | axios 0.32.0 fixed in 0.33.0, 1.18.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-64756 | MEDIUM4.5 | glob 10.3.16 fixed in 11.1.0, 10.5.0 | 3.1% Low-Moderate Risk | Directly Exposed |
| GHSA-2x7j-588g-ccc2 | MEDIUM4.5 | nodemailer 7.0.13 fixed in 9.1.0 | — | Directly Exposed |
| GHSA-v53p-9fqp-m79j | MEDIUM4.5 | nodemailer 7.0.13 fixed in 10.0.6 | — | Directly Exposed |
| CVE-2026-59873 | MEDIUM4.5 | tar 6.2.1 fixed in 7.5.19 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-59874 | MEDIUM4.5 | tar 6.2.1 fixed in 7.5.18 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-73566 | MEDIUM4.5 | tar 6.2.1 fixed in 7.5.21 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59871 | MEDIUM4.5 | tar 6.2.1 fixed in 7.5.18 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | MEDIUM4.44 | libssl3 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-69248 | MEDIUM4.44 | python3-cryptography 38.0.4-3+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102271 | MEDIUM4.44 | python3-jwt 2.6.0-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48526 | MEDIUM4.44 | python3-jwt 2.6.0-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-101916 | MEDIUM4.44 | @grpc/grpc-js 1.8.22 fixed in 1.13.6, 1.14.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-67316 | MEDIUM4.44 | axios 0.32.0 fixed in 1.18.0, 0.33.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-96674 | MEDIUM4.4 | libasound2 1.2.8-1+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-96674 | MEDIUM4.4 | libasound2-data 1.2.8-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM4.38 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM4.38 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-12912 | MEDIUM4.38 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52490 | MEDIUM4.38 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-107823 | MEDIUM4.32 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-107823 | MEDIUM4.32 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-107823 | MEDIUM4.32 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-107823 | MEDIUM4.32 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-107823 | MEDIUM4.32 | mariadb-server 1:10.11.19-0+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-107823 | MEDIUM4.32 | mariadb-server-core 1:10.11.19-0+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-7246 | MEDIUM4.32 | python3-click 8.1.3-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-25068 | MEDIUM4.3 | libasound2 1.2.8-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25068 | MEDIUM4.3 | libasound2-data 1.2.8-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM4.26 | libacl1 2.3.1-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM4.26 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM4.26 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM4.26 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM4.26 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-94286 | MEDIUM4.26 | libxtst6 2:1.2.3-1.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-82659 | MEDIUM4.26 | nodemailer 7.0.13 fixed in 9.0.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-26960 | MEDIUM4.26 | tar 6.2.1 fixed in 7.5.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-2950 | MEDIUM4.24 | lodash 4.17.23 fixed in 4.18.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-44288 | MEDIUM4.24 | protobufjs 7.2.6 fixed in 7.5.6, 8.0.2 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-44292 | MEDIUM4.24 | protobufjs 7.2.6 fixed in 7.5.6, 8.0.2 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-44294 | MEDIUM4.24 | protobufjs 7.2.6 fixed in 7.5.6, 8.0.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54269 | MEDIUM4.24 | protobufjs 7.2.6 fixed in 7.6.3, 8.6.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53613 | MEDIUM4.2 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libfdisk1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libfdisk1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | nscd 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | nscd 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | MEDIUM4.08 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86410 | MEDIUM4.08 | curl 7.88.1-10+deb12u15 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | MEDIUM4.08 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86410 | MEDIUM4.08 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-49265 | MEDIUM4.08 | python3-oauthlib 3.2.2-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-61915 | MEDIUM4.02 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107821 | MEDIUM4.02 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107821 | MEDIUM4.02 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107821 | MEDIUM4.02 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107821 | MEDIUM4.02 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107821 | MEDIUM4.02 | mariadb-server 1:10.11.19-0+deb12u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107821 | MEDIUM4.02 | mariadb-server-core 1:10.11.19-0+deb12u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-115506 | MEDIUM4 | libexpat1 2.5.0-1+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107080 | MEDIUM4 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-114583 | MEDIUM4 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-114583 | MEDIUM4 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11856 | LOW3.9 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-19931 | LOW3.9 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5545 | LOW3.9 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6429 | LOW3.9 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8924 | LOW3.9 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW3.9 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW3.9 | curl 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-107886 | LOW3.9 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34978 | LOW3.9 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11856 | LOW3.9 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-19931 | LOW3.9 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5545 | LOW3.9 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6429 | LOW3.9 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8924 | LOW3.9 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW3.9 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW3.9 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | LOW3.9 | libncurses6 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-50495 | LOW3.9 | libncursesw6 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6277 | LOW3.9 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-50495 | LOW3.9 | libtinfo6 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-94283 | LOW3.9 | libx11-6 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94283 | LOW3.9 | libx11-data 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94283 | LOW3.9 | libx11-xcb1 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | LOW3.9 | ncurses-base 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-50495 | LOW3.9 | ncurses-bin 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-26007 | LOW3.9 | python3-cryptography 38.0.4-3+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | LOW3.9 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.9 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-82662 | LOW3.9 | nodemailer 7.0.13 fixed in 8.0.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-110871 | LOW3.9 | nodemailer 7.0.13 fixed in 10.0.10 | 0.4% Theoretical Threat | Directly Exposed |
| GHSA-85x2-q946-cp5h | LOW3.9 | nodemailer 7.0.13 fixed in 10.1.4 | — | Directly Exposed |
| GHSA-8c8m-p3m8-cjg8 | LOW3.9 | nodemailer 7.0.13 fixed in 10.1.4 | — | Directly Exposed |
| GHSA-cc9r-2j5m-2m83 | LOW3.9 | nodemailer 7.0.13 fixed in 9.1.0 | — | Directly Exposed |
| GHSA-m943-m63m-w62w | LOW3.9 | nodemailer 7.0.13 fixed in 10.1.4 | — | Directly Exposed |
| GHSA-wmmp-3585-3rmp | LOW3.9 | nodemailer 7.0.13 fixed in 9.1.0 | — | Directly Exposed |
| CVE-2016-1585 | LOW3.9 | libapparmor1 3.0.8-3 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56109 | LOW3.9 | libasound2 1.2.8-1+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56109 | LOW3.9 | libasound2-data 1.2.8-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | LOW3.9 | libcairo-gobject2 1.16.0-7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | LOW3.9 | libcairo-gobject2 1.16.0-7 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6461 | LOW3.9 | libcairo-gobject2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6462 | LOW3.9 | libcairo-gobject2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | LOW3.9 | libcairo2 1.16.0-7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | LOW3.9 | libcairo2 1.16.0-7 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6461 | LOW3.9 | libcairo2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6462 | LOW3.9 | libcairo2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-19617 | LOW3.9 | libdevmapper1.02.1 2:1.02.185-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-6829 | LOW3.9 | libgcrypt20 1.10.1-3+deb12u1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | LOW3.9 | libgcrypt20 1.10.1-3+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-67693 | LOW3.9 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88647 | LOW3.9 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88648 | LOW3.9 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95184 | LOW3.9 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW3.9 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW3.9 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW3.9 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2012-2663 | LOW3.9 | libip4tc2 1.8.9-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-9937 | LOW3.9 | libjbig0 2.1-6.1 No fix yet | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | LOW3.9 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW3.9 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW3.9 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW3.9 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW3.9 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW3.9 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW3.9 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW3.9 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW3.9 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2016-10505 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9113 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9114 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9115 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9116 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9117 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9580 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9581 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2018-16376 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6988 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2025-28162 | LOW3.9 | libpng16-16 1.6.39-2+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-28164 | LOW3.9 | libpng16-16 1.6.39-2+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | LOW3.9 | libpng16-16 1.6.39-2+deb12u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-12003 | LOW3.9 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-12003 | LOW3.9 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2012-2663 | LOW3.9 | libxtables12 1.8.9-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | nscd 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | nscd 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | nscd 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | nscd 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | nscd 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | nscd 2.36-9+deb12u14 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | nscd 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-39689 | LOW3.9 | python3-certifi 2022.9.24-1 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107822 | LOW3.84 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107822 | LOW3.84 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107822 | LOW3.84 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107822 | LOW3.84 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107822 | LOW3.84 | mariadb-server 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107822 | LOW3.84 | mariadb-server-core 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | LOW3.78 | libacl1 2.3.1-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27447 | LOW3.78 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-12345 | LOW3.78 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12345 | LOW3.78 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-29786 | LOW3.78 | tar 6.2.1 fixed in 7.5.10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-39314 | LOW3.72 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39316 | LOW3.72 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-3374 | LOW3.7 | libapt-pkg6.0 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW3.7 | libexpat1 2.5.0-1+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.7 | libssl3 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | nscd 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-82562 | LOW3.7 | qs 6.14.2 fixed in 6.16.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18495 | LOW3.66 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-49264 | LOW3.66 | python3-oauthlib 3.2.2-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23745 | LOW3.66 | tar 6.2.1 fixed in 7.5.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-6135 | LOW3.65 | libnss3 2:3.87.1-1+deb12u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-39327 | LOW3.65 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | LOW3.54 | openssl 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75805 | LOW3.54 | openssl 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-77696 | LOW3.54 | openssl 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-101902 | LOW3.54 | axios 0.32.0 fixed in 0.34.0, 1.20.0 | 0.4% Theoretical Threat | Directly Exposed |
| GHSA-6vj9-mwq6-2f5v | LOW3.54 | nodemailer 7.0.13 fixed in 10.0.2 | — | Directly Exposed |
| GHSA-8m3c-c648-2xjj | LOW3.54 | nodemailer 7.0.13 fixed in 9.1.1 | — | Directly Exposed |
| GHSA-8vvx-rff5-p5rq | LOW3.54 | nodemailer 7.0.13 fixed in 10.0.2 | — | Directly Exposed |
| CVE-2026-104844 | LOW3.54 | postcss-selector-parser 7.1.1 fixed in 7.1.6, 6.1.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-23950 | LOW3.54 | tar 6.2.1 fixed in 7.5.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | LOW3.53 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-113010 | LOW3.44 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113035 | LOW3.44 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113050 | LOW3.44 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113054 | LOW3.44 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113151 | LOW3.44 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113277 | LOW3.44 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113029 | LOW3.44 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113140 | LOW3.44 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113010 | LOW3.44 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113035 | LOW3.44 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113050 | LOW3.44 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113054 | LOW3.44 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113151 | LOW3.44 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113277 | LOW3.44 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113029 | LOW3.44 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113140 | LOW3.44 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-55480 | LOW3.42 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW3.42 | libperl5.36 5.36.0-7+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW3.42 | perl 5.36.0-7+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW3.42 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW3.42 | perl-modules-5.36 5.36.0-7+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-29481 | LOW3.31 | libbpf1 1:1.1.2-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.31 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | LOW3.31 | libelf1 0.188-2.1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1365 | LOW3.31 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | LOW3.31 | libelf1 0.188-2.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1372 | LOW3.31 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | LOW3.31 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | LOW3.31 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52426 | LOW3.31 | libexpat1 2.5.0-1+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW3.31 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW3.31 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW3.31 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW3.31 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-26924 | LOW3.31 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-29932 | LOW3.31 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-29933 | LOW3.31 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-29934 | LOW3.31 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-29935 | LOW3.31 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-29939 | LOW3.31 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-29941 | LOW3.31 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-29942 | LOW3.31 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-31852 | LOW3.31 | libllvm15 1:15.0.6-4+b1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2017-11695 | LOW3.31 | libnss3 2:3.87.1-1+deb12u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2017-11696 | LOW3.31 | libnss3 2:3.87.1-1+deb12u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2017-11697 | LOW3.31 | libnss3 2:3.87.1-1+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-11698 | LOW3.31 | libnss3 2:3.87.1-1+deb12u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-37769 | LOW3.31 | libpixman-1-0 0.42.2-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | LOW3.31 | libpng16-16 1.6.39-2+deb12u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libsystemd-shared 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libsystemd-shared 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libsystemd-shared 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-23491 | LOW3.31 | python3-certifi 2022.9.24-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-37920 | LOW3.31 | python3-certifi 2022.9.24-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-58436 | LOW3.3 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107885 | LOW3.3 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107888 | LOW3.3 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107890 | LOW3.3 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | LOW3.3 | libpam-systemd 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-50812 | LOW3.3 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50813 | LOW3.3 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94284 | LOW3.3 | libx11-6 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94284 | LOW3.3 | libx11-data 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94284 | LOW3.3 | libx11-xcb1 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | LOW3.3 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW3.3 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-50812 | LOW3.3 | sqlite3 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50813 | LOW3.3 | sqlite3 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5704 | LOW3.3 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | LOW3.3 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31802 | LOW3.3 | tar 6.2.1 fixed in 7.5.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53655 | LOW3.3 | tar 6.2.1 fixed in 7.5.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW3.3 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW3.3 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libsystemd-shared 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libudev1 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3449 | LOW3.3 | @tootallnate/once 1.1.2 fixed in 3.0.1, 2.0.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40468 | LOW3.28 | gawk 1:5.2.1-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-40469 | LOW3.28 | gawk 1:5.2.1-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-58016 | LOW3.28 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-41079 | LOW3.24 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | LOW3.24 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | LOW3.24 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | LOW3.24 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | LOW3.24 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | LOW3.24 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | LOW3.24 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | LOW3.24 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | LOW3.24 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | LOW3.24 | mariadb-server 1:10.11.19-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | LOW3.24 | mariadb-server 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | LOW3.24 | mariadb-server-core 1:10.11.19-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | LOW3.24 | mariadb-server-core 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-102269 | LOW3.24 | python3-jwt 2.6.0-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48758 | LOW3.24 | @sigstore/core 2.0.0 fixed in 3.2.1 | 0.2% Theoretical Threat | Post-Exploit |
| GHSA-268h-hp4c-crq3 | LOW3.24 | nodemailer 7.0.13 fixed in 8.0.9 | — | Directly Exposed |
| GHSA-wqvq-jvpq-h66f | LOW3.24 | nodemailer 7.0.13 fixed in 8.0.9 | — | Directly Exposed |
| CVE-2026-112992 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-112994 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-112995 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-112996 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-112997 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-112998 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-112999 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113000 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113001 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113002 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113003 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113004 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113005 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113007 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113008 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113009 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113012 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113013 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113014 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113015 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113016 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113018 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113019 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113020 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113021 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113022 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113023 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113024 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113026 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113027 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113028 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113031 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113032 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113034 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113036 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113038 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113040 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113041 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113042 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113044 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113045 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113046 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113047 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113048 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113049 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113051 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113052 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113053 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113055 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113056 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113058 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113059 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113060 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113061 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113062 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113063 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113064 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113065 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113066 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113067 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113069 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113070 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113071 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113072 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113075 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113076 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113077 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113078 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113079 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113080 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113083 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113084 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113085 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113086 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113087 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113088 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113089 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113090 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113092 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113093 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113094 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113095 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113096 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113097 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113098 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113099 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113100 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113101 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113102 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113103 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113104 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113105 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113107 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113108 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113109 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113110 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113111 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113112 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113114 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113116 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113118 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113119 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113120 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113121 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113122 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113123 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113124 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113125 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113126 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113127 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113129 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113131 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113132 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113133 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113135 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113136 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113138 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113139 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113141 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113142 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113144 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113145 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113146 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113147 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113148 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113149 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113150 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113152 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113153 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113154 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113155 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113156 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113158 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113159 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113160 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113162 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113163 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113164 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113166 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113167 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113168 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113169 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113170 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113171 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113172 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113173 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113174 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113175 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113176 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113177 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113178 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113179 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113180 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113181 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113182 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113183 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113184 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113185 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113186 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113187 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113188 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113189 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113190 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113191 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113192 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113193 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113194 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113195 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113196 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113197 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113198 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113199 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113201 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113202 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113203 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113204 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113205 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113206 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113208 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113209 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113211 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113212 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113213 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113214 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113215 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113218 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113219 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113220 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113221 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113222 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113223 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113224 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113225 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113226 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113227 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113228 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113229 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113230 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113231 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113232 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113235 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113236 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113237 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113238 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113239 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113240 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113241 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113243 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113244 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113245 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113246 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113247 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113248 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113249 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113251 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113253 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113254 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113255 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113256 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113257 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113258 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113259 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113260 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113261 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113262 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113263 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113265 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113267 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113268 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113269 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113270 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113271 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113272 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113275 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113276 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113279 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113280 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113281 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113282 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113283 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113284 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113286 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113287 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113288 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113289 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113290 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113291 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113292 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113294 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113296 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113297 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113298 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113299 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113300 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113301 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113302 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113303 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113304 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113306 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113307 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113308 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113309 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113310 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113311 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113312 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113313 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113316 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113317 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113318 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113320 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113322 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113325 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113326 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113327 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113328 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113329 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113330 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113331 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113332 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113333 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113335 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113336 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113337 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113338 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113339 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113342 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113343 | LOW3.2 | chromium 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-112992 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-112994 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-112995 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-112996 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-112997 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-112998 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-112999 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113000 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113001 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113002 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113003 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113004 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113005 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113007 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113008 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113009 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113012 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113013 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113014 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113015 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113016 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113018 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113019 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113020 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113021 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113022 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113023 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113024 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113026 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113027 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113028 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113031 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113032 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113034 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113036 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113038 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113040 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113041 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113042 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113044 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113045 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113046 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113047 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113048 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113049 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113051 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113052 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113053 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113055 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113056 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113058 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113059 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113060 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113061 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113062 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113063 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113064 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113065 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113066 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113067 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113069 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113070 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113071 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113072 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113075 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113076 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113077 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113078 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113079 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113080 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113083 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113084 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113085 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113086 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113087 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113088 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113089 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113090 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113092 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113093 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113094 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113095 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113096 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113097 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113098 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113099 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113100 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113101 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113102 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113103 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113104 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113105 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113107 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113108 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113109 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113110 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113111 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113112 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113114 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113116 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113118 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113119 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113120 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113121 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113122 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113123 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113124 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113125 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113126 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113127 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113129 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113131 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113132 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113133 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113135 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113136 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113138 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113139 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113141 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113142 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113144 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113145 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113146 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113147 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113148 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113149 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113150 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113152 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113153 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113154 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113155 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113156 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113158 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113159 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113160 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113162 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113163 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113164 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113166 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113167 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113168 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113169 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113170 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113171 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113172 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113173 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113174 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113175 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113176 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113177 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113178 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113179 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113180 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113181 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113182 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113183 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113184 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113185 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113186 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113187 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113188 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113189 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113190 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113191 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113192 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113193 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113194 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113195 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113196 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113197 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113198 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113199 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113201 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113202 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113203 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113204 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113205 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113206 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113208 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113209 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113211 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113212 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113213 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113214 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113215 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113218 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113219 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113220 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113221 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113222 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113223 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113224 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113225 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113226 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113227 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113228 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113229 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113230 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113231 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113232 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113235 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113236 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113237 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113238 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113239 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113240 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113241 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113243 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113244 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113245 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113246 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113247 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113248 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113249 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113251 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113253 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113254 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113255 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113256 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113257 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113258 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113259 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113260 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113261 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113262 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113263 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113265 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113267 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113268 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113269 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113270 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113271 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113272 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113275 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113276 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113279 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113280 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113281 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113282 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113283 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113284 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113286 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113287 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113288 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113289 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113290 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113291 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113292 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113294 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113296 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113297 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113298 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113299 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113300 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113301 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113302 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113303 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113304 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113306 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113307 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113308 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113309 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113310 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113311 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113312 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113313 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113316 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113317 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113318 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113320 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113322 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113325 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113326 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113327 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113328 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113329 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113330 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113331 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113332 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113333 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113335 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113336 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113337 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113338 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113339 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113342 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113343 | LOW3.2 | chromium-common 155.0.8059.79-1~deb12u1 fixed in 156.0.8078.47-1~deb12u1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-13595 | LOW3.18 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4873 | LOW3.18 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6253 | LOW3.18 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-86409 | LOW3.18 | curl 7.88.1-10+deb12u15 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34979 | LOW3.18 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-61702 | LOW3.18 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4873 | LOW3.18 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6253 | LOW3.18 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-86409 | LOW3.18 | libcurl4 7.88.1-10+deb12u15 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libfdisk1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libfdisk1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | mount 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | LOW3.18 | openssl 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34073 | LOW3.18 | python3-cryptography 38.0.4-3+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102265 | LOW3.18 | python3-jwt 2.6.0-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48525 | LOW3.18 | python3-jwt 2.6.0-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | LOW3.18 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW3.18 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW3.18 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW3.18 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW3.18 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59875 | LOW3.18 | tar 6.2.1 fixed in 7.5.17 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-92262 | LOW3.17 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-97380 | LOW3.17 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-16742 | LOW3.17 | libpam-systemd 252.39-1~deb12u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-92262 | LOW3.17 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-97380 | LOW3.17 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-92262 | LOW3.17 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-97380 | LOW3.17 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-92262 | LOW3.17 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-97380 | LOW3.17 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-92262 | LOW3.17 | mariadb-server 1:10.11.19-0+deb12u1 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-97380 | LOW3.17 | mariadb-server 1:10.11.19-0+deb12u1 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-92262 | LOW3.17 | mariadb-server-core 1:10.11.19-0+deb12u1 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-97380 | LOW3.17 | mariadb-server-core 1:10.11.19-0+deb12u1 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-7883 | LOW3.15 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34990 | LOW3.12 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | LOW3.1 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-69192 | LOW3.1 | ip-address 10.1.0 fixed in 10.3.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-59180 | LOW3.1 | apprise 2.0.0-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-74860 | LOW3.06 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-94285 | LOW3.06 | libx11-6 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94285 | LOW3.06 | libx11-data 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94285 | LOW3.06 | libx11-xcb1 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107818 | LOW3.02 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-107818 | LOW3.02 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-107818 | LOW3.02 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-107818 | LOW3.02 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-107818 | LOW3.02 | mariadb-server 1:10.11.19-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-107818 | LOW3.02 | mariadb-server-core 1:10.11.19-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-85091 | LOW3 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-88807 | LOW2.99 | libxrender1 1:0.9.10-1.1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58010 | LOW2.95 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58012 | LOW2.95 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58013 | LOW2.95 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-37555 | LOW2.95 | libsndfile1 1.2.0-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-70456 | LOW2.95 | rsync 3.2.7-1+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-70457 | LOW2.95 | rsync 3.2.7-1+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-70458 | LOW2.95 | rsync 3.2.7-1+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-70461 | LOW2.95 | rsync 3.2.7-1+deb12u6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-24842 | LOW2.95 | tar 6.2.1 fixed in 7.5.7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-102270 | LOW2.94 | python3-jwt 2.6.0-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| GHSA-vvjj-xcjg-gr5g | LOW2.94 | nodemailer 7.0.13 fixed in 8.0.5 | — | Directly Exposed |
| CVE-2026-8286 | LOW2.92 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | LOW2.92 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53783 | LOW2.92 | rsync 3.2.7-1+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53789 | LOW2.92 | rsync 3.2.7-1+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53790 | LOW2.92 | rsync 3.2.7-1+deb12u6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-53795 | LOW2.92 | rsync 3.2.7-1+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-70460 | LOW2.92 | rsync 3.2.7-1+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-70463 | LOW2.92 | rsync 3.2.7-1+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-107928 | LOW2.88 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-107928 | LOW2.88 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | LOW2.88 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.82 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-10536 | LOW2.82 | curl 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.82 | gzip 1.12-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-10536 | LOW2.82 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libfdisk1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | LOW2.81 | libncurses6 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libncursesw6 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libtinfo6 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-86138 | LOW2.81 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86140 | LOW2.81 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86142 | LOW2.81 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86144 | LOW2.81 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-base 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-bin 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-11822 | LOW2.81 | sqlite3 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-96512 | LOW2.81 | sudo 1.9.13p3-1+deb12u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-50422 | LOW2.8 | libcairo-gobject2 1.16.0-7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo2 1.16.0-7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-4016 | LOW2.8 | libproc2-0 2:4.0.2-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd-shared 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40467 | LOW2.7 | gawk 1:5.2.1-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-40553 | LOW2.7 | gawk 1:5.2.1-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW2.7 | gzip 1.12-1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-58011 | LOW2.7 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58015 | LOW2.7 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-25193 | LOW2.7 | libharfbuzz-subset0 6.0.0+dfsg-3 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-25193 | LOW2.7 | libharfbuzz0b 6.0.0+dfsg-3 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-9538 | LOW2.7 | perl 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW2.7 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW2.7 | perl-modules-5.36 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW2.7 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW2.7 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-70455 | LOW2.7 | rsync 3.2.7-1+deb12u6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-70464 | LOW2.7 | rsync 3.2.7-1+deb12u6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-102276 | LOW2.7 | brace-expansion 2.0.2 fixed in 5.0.10, 3.0.7, 2.1.5, 1.1.19 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-102278 | LOW2.7 | brace-expansion 2.0.2 fixed in 5.0.11, 3.0.8, 2.1.6, 1.1.20 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-14257 | LOW2.7 | brace-expansion 2.0.2 fixed in 5.0.8, 3.0.3, 2.1.3, 1.1.17 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-69152 | LOW2.7 | brace-expansion 2.0.2 fixed in 1.1.18, 2.1.4, 3.0.6, 5.0.9 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-33750 | LOW2.7 | brace-expansion 2.0.2 fixed in 5.0.5, 3.0.2, 2.0.3, 1.1.13 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-93748 | LOW2.7 | http-cache-semantics 4.2.0 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9496 | LOW2.7 | pacote 19.0.2 fixed in 21.5.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9496 | LOW2.7 | pacote 20.0.1 fixed in 21.5.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-33671 | LOW2.7 | picomatch 4.0.3 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48815 | LOW2.7 | sigstore 3.1.0 fixed in 4.1.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-84782 | LOW2.66 | openssl 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-53791 | LOW2.66 | rsync 3.2.7-1+deb12u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53793 | LOW2.66 | rsync 3.2.7-1+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-70452 | LOW2.66 | rsync 3.2.7-1+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.65 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2022-27943 | LOW2.65 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2022-27943 | LOW2.65 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107817 | LOW2.64 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107817 | LOW2.64 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107817 | LOW2.64 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107817 | LOW2.64 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107817 | LOW2.64 | mariadb-server 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107817 | LOW2.64 | mariadb-server-core 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18477 | LOW2.64 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18508 | LOW2.64 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86143 | LOW2.63 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-11940 | LOW2.63 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-11940 | LOW2.63 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-87875 | LOW2.58 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW2.58 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW2.58 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW2.58 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW2.58 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW2.58 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW2.58 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW2.58 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW2.58 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW2.58 | mariadb-server 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW2.58 | mariadb-server 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW2.58 | mariadb-server-core 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW2.58 | mariadb-server-core 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9358 | LOW2.58 | postcss-selector-parser 7.1.1 fixed in 6.1.3, 7.1.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-16118 | LOW2.56 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW2.56 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW2.56 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW2.56 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW2.56 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53784 | LOW2.56 | rsync 3.2.7-1+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53785 | LOW2.56 | rsync 3.2.7-1+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53802 | LOW2.56 | rsync 3.2.7-1+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7709 | LOW2.55 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-7709 | LOW2.55 | sqlite3 3.40.1-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | LOW2.52 | libc-bin 2.36-9+deb12u14 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95818 | LOW2.52 | libc-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86805 | LOW2.52 | libc6 2.36-9+deb12u14 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95818 | LOW2.52 | libc6 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86805 | LOW2.52 | nscd 2.36-9+deb12u14 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95818 | LOW2.52 | nscd 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53803 | LOW2.52 | rsync 3.2.7-1+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-48522 | LOW2.52 | python3-jwt 2.6.0-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-45931 | LOW2.5 | libgbm1 22.3.6-1+deb12u2 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45931 | LOW2.5 | libgl1-mesa-dri 22.3.6-1+deb12u2 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45931 | LOW2.5 | libglapi-mesa 22.3.6-1+deb12u2 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45931 | LOW2.5 | libglx-mesa0 22.3.6-1+deb12u2 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-95209 | LOW2.5 | libgnutls30 3.7.9-2+deb12u7 No fix yet | — | Directly Exposed |
| CVE-2026-95210 | LOW2.5 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18739 | LOW2.5 | libpopt0 1.19+dfsg-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18743 | LOW2.5 | libpopt0 1.19+dfsg-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-115557 | LOW2.5 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-115557 | LOW2.5 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | LOW2.45 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-19499 | LOW2.45 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-19499 | LOW2.45 | nscd 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-70454 | LOW2.45 | rsync 3.2.7-1+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-107655 | LOW2.4 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| TEMP-0000000-3F659E | LOW2.4 | libcups2 2.4.2-3+deb12u9 No fix yet | — | Directly Exposed |
| TEMP-0000000-51E1F8 | LOW2.4 | libcups2 2.4.2-3+deb12u9 No fix yet | — | Directly Exposed |
| TEMP-0000000-71B844 | LOW2.4 | libcups2 2.4.2-3+deb12u9 No fix yet | — | Directly Exposed |
| TEMP-0000000-EC06A3 | LOW2.4 | libcups2 2.4.2-3+deb12u9 No fix yet | — | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | libperl5.36 5.36.0-7+deb12u4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | perl 5.36.0-7+deb12u4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | perl-modules-5.36 5.36.0-7+deb12u4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-114583 | LOW2.4 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-114583 | LOW2.4 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW2.34 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW2.34 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW2.34 | nscd 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53786 | LOW2.34 | rsync 3.2.7-1+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53792 | LOW2.34 | rsync 3.2.7-1+deb12u6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-70453 | LOW2.34 | rsync 3.2.7-1+deb12u6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-70462 | LOW2.34 | rsync 3.2.7-1+deb12u6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW2.34 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56391 | LOW2.34 | coreutils 9.1-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.34 | coreutils 9.1-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-2379 | LOW2.34 | curl 7.88.1-10+deb12u15 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-0725 | LOW2.34 | curl 7.88.1-10+deb12u15 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14017 | LOW2.34 | curl 7.88.1-10+deb12u15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | LOW2.34 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | LOW2.34 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW2.34 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102473 | LOW2.34 | dash 0.5.12-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-102474 | LOW2.34 | dash 0.5.12-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.34 | diffutils 1:3.8-4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-19617 | LOW2.34 | dmsetup 2:1.02.185-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-47268 | LOW2.34 | iputils-ping 3:20221126-1+deb12u1 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2025-14104 | LOW2.34 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2014-8166 | LOW2.34 | libcups2 2.4.2-3+deb12u9 No fix yet | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2379 | LOW2.34 | libcurl4 7.88.1-10+deb12u15 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-0725 | LOW2.34 | libcurl4 7.88.1-10+deb12u15 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14017 | LOW2.34 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | LOW2.34 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | LOW2.34 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW2.34 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | libfdisk1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2015-3276 | LOW2.34 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | LOW2.34 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-15719 | LOW2.34 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-22185 | LOW2.34 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31486 | LOW2.34 | libperl5.36 5.36.0-7+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | LOW2.34 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16232 | LOW2.34 | libtiff6 4.5.0-6+deb12u4 No fix yet | 5.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-10126 | LOW2.34 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1210 | LOW2.34 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-61143 | LOW2.34 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | LOW2.34 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | LOW2.34 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52491 | LOW2.34 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52492 | LOW2.34 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31486 | LOW2.34 | perl 5.36.0-7+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-31486 | LOW2.34 | perl-base 5.36.0-7+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-31486 | LOW2.34 | perl-modules-5.36 5.36.0-7+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-12003 | LOW2.34 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-12003 | LOW2.34 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-45346 | LOW2.34 | sqlite3 3.40.1-2+deb12u2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-82474 | LOW2.34 | sudo 1.9.13p3-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2005-2541 | LOW2.34 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53796 | LOW2.27 | rsync 3.2.7-1+deb12u6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53799 | LOW2.27 | rsync 3.2.7-1+deb12u6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-13608 | LOW2.22 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | curl 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | curl 7.88.1-10+deb12u15 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-87865 | LOW2.22 | curl 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-87866 | LOW2.22 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | curl 7.88.1-10+deb12u15 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13608 | LOW2.22 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-87865 | LOW2.22 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-87866 | LOW2.22 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | libcurl4 7.88.1-10+deb12u15 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-35189 | LOW2.22 | openssl 3.0.22-1~deb12u1 fixed in 3.0.22-1~deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48524 | LOW2.22 | python3-jwt 2.6.0-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-101915 | LOW2.22 | @grpc/grpc-js 1.8.22 fixed in 1.13.6, 1.14.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-67319 | LOW2.22 | axios 0.32.0 fixed in 0.33.0, 1.18.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42338 | LOW2.2 | ip-address 10.1.0 fixed in 10.1.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18839 | LOW2.2 | libpopt0 1.19+dfsg-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6879 | LOW2.2 | libpython3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6879 | LOW2.2 | libpython3.11-stdlib 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53801 | LOW2.12 | rsync 3.2.7-1+deb12u6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-45913 | LOW2.12 | libgbm1 22.3.6-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-45919 | LOW2.12 | libgbm1 22.3.6-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-45922 | LOW2.12 | libgbm1 22.3.6-1+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-45924 | LOW2.12 | libgl1 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-45913 | LOW2.12 | libgl1-mesa-dri 22.3.6-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-45919 | LOW2.12 | libgl1-mesa-dri 22.3.6-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-45922 | LOW2.12 | libgl1-mesa-dri 22.3.6-1+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-45913 | LOW2.12 | libglapi-mesa 22.3.6-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-45919 | LOW2.12 | libglapi-mesa 22.3.6-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-45922 | LOW2.12 | libglapi-mesa 22.3.6-1+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-45924 | LOW2.12 | libglvnd0 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-45913 | LOW2.12 | libglx-mesa0 22.3.6-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-45919 | LOW2.12 | libglx-mesa0 22.3.6-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-45922 | LOW2.12 | libglx-mesa0 22.3.6-1+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-45924 | LOW2.12 | libglx0 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-29070 | LOW2.12 | liblcms2-2 2.14-2+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-27587 | LOW2.12 | libssl3 3.0.22-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-50613 | LOW1.99 | libsndfile1 1.2.0-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-2781 | LOW1.99 | coreutils 9.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW1.99 | coreutils 9.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW1.99 | coreutils 9.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW1.99 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-10966 | LOW1.99 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libfdisk1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | LOW1.99 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW1.99 | libpam-systemd 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-31438 | LOW1.99 | libpam-systemd 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-31439 | LOW1.99 | libpam-systemd 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-29088 | LOW1.99 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-1916 | LOW1.99 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-3164 | LOW1.99 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6228 | LOW1.99 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | LOW1.99 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | LOW1.99 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8851 | LOW1.99 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2007-5686 | LOW1.99 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2007-5686 | LOW1.99 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-54661 | LOW1.99 | socat 1.7.4.4-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-29088 | LOW1.99 | sqlite3 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-42465 | LOW1.99 | sudo 1.9.13p3-1+deb12u4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-88372 | LOW1.98 | libsndfile1 1.2.0-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-88386 | LOW1.98 | libsndfile1 1.2.0-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76781 | LOW1.98 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-94266 | LOW1.98 | curl 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-94266 | LOW1.98 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW1.98 | libpam-systemd 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-70873 | LOW1.98 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW1.98 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.98 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-70873 | LOW1.98 | sqlite3 3.40.1-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-15588 | LOW1.91 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-86469 | LOW1.91 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22693 | LOW1.91 | libharfbuzz-subset0 6.0.0+dfsg-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-22693 | LOW1.91 | libharfbuzz0b 6.0.0+dfsg-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-56226 | LOW1.91 | libsndfile1 1.2.0-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53794 | LOW1.91 | rsync 3.2.7-1+deb12u6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-53798 | LOW1.91 | rsync 3.2.7-1+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-70459 | LOW1.91 | rsync 3.2.7-1+deb12u6 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-13149 | LOW1.91 | brace-expansion 2.0.2 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-102277 | LOW1.91 | brace-expansion 2.0.2 fixed in 5.0.12, 3.0.9, 2.1.7, 1.1.21 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-101911 | LOW1.91 | ip-address 10.1.0 fixed in 10.7.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-101912 | LOW1.91 | ip-address 10.1.0 fixed in 10.7.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-101913 | LOW1.91 | ip-address 10.1.0 fixed in 10.5.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-111997 | LOW1.91 | ip-address 10.1.0 fixed in 10.7.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-33672 | LOW1.91 | picomatch 4.0.3 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.86 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-82209 | LOW1.86 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-56433 | LOW1.84 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-87876 | LOW1.8 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-57062 | LOW1.74 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53788 | LOW1.73 | rsync 3.2.7-1+deb12u6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53797 | LOW1.69 | rsync 3.2.7-1+deb12u6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53800 | LOW1.69 | rsync 3.2.7-1+deb12u6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.68 | libncurses6 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | libncursesw6 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW1.68 | libpam-systemd 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | libperl5.36 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-8961 | LOW1.68 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9165 | LOW1.68 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | libtinfo6 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | ncurses-base 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | ncurses-bin 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | perl 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | perl-modules-5.36 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-4016 | LOW1.68 | procps 2:4.0.2-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| TEMP-0841856-B18BAF | LOW1.5 | bash 5.2.15-2+b13 No fix yet | — | Post-Exploit |
| CVE-2026-105326 | LOW1.5 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55467 | LOW1.5 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| TEMP-0628843-DBAD28 | LOW1.5 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | — | Post-Exploit |
| TEMP-0628843-DBAD28 | LOW1.5 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | — | Post-Exploit |
| CVE-2026-115557 | LOW1.5 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-115557 | LOW1.5 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| TEMP-0517018-A83CE6 | LOW1.5 | sysvinit-utils 3.06-4 No fix yet | — | Post-Exploit |
| TEMP-0290435-0B57B5 | LOW1.5 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2012-0039 | LOW1.4 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-109828 | LOW1.4 | libsndfile1 1.2.0-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-11979 | LOW1.4 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| GHSA-c7w3-x93f-qmm8 | LOW1.38 | nodemailer 7.0.13 fixed in 8.0.4 | — | Directly Exposed |
| CVE-2026-6879 | LOW1.32 | python3.11 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6879 | LOW1.32 | python3.11-minimal 3.11.2-6+deb12u9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-13978 | LOW1.27 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW1.27 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-27587 | LOW1.27 | openssl 3.0.22-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-45768 | LOW1.27 | python3-jwt 2.6.0-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2005-1119 | LOW1.07 | sudo 1.9.13p3-1+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-68121 | NONE0 | stdlib v1.20.5 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-24790 | NONE0 | stdlib v1.20.5 fixed in 1.21.11, 1.22.4 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-22871 | NONE0 | stdlib v1.20.5 fixed in 1.23.8, 1.24.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-16742 | NONE0 | systemd 252.39-1~deb12u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-16742 | NONE0 | systemd-sysv 252.39-1~deb12u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-39821 | NONE0 | stdlib v1.20.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-56858 | NONE0 | stdlib v1.20.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39822 | NONE0 | stdlib v1.20.5 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-39325 | NONE0 | stdlib v1.20.5 fixed in 1.20.10, 1.21.3 | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-45283 | NONE0 | stdlib v1.20.5 fixed in 1.20.11, 1.21.4, 1.20.12, 1.21.5 | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-45288 | NONE0 | stdlib v1.20.5 fixed in 1.21.9, 1.22.2 | 89.5% Actively Exploited | Not Applicable |
| CVE-2024-34156 | NONE0 | stdlib v1.20.5 fixed in 1.22.7, 1.23.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-61726 | NONE0 | stdlib v1.20.5 fixed in 1.24.12, 1.25.6 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-61729 | NONE0 | stdlib v1.20.5 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25679 | NONE0 | stdlib v1.20.5 fixed in 1.25.8, 1.26.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.20.5 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32280 | NONE0 | stdlib v1.20.5 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32281 | NONE0 | stdlib v1.20.5 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32283 | NONE0 | stdlib v1.20.5 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33811 | NONE0 | stdlib v1.20.5 fixed in 1.25.10, 1.26.3 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | stdlib v1.20.5 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33818 | NONE0 | stdlib v1.20.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-39820 | NONE0 | stdlib v1.20.5 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39836 | NONE0 | stdlib v1.20.5 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.20.5 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.20.5 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56853 | NONE0 | stdlib v1.20.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56859 | NONE0 | stdlib v1.20.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56860 | NONE0 | stdlib v1.20.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56862 | NONE0 | stdlib v1.20.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78667 | NONE0 | stdlib v1.20.5 fixed in 1.26.9, 1.27.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-78669 | NONE0 | stdlib v1.20.5 fixed in 1.26.9, 1.27.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-97031 | NONE0 | stdlib v1.20.5 fixed in 1.26.9, 1.27.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-58183 | NONE0 | stdlib v1.20.5 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58188 | NONE0 | stdlib v1.20.5 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61728 | NONE0 | stdlib v1.20.5 fixed in 1.24.12, 1.25.6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.20.5 fixed in 1.26.9, 1.27.2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.20.5 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.20.5 fixed in 1.26.9, 1.27.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-4055 | NONE0 | xdg-utils 1.1.3-4.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-47907 | NONE0 | stdlib v1.20.5 fixed in 1.23.12, 1.24.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-111943 | NONE0 | stdlib v1.20.5 fixed in 1.26.10, 1.27.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-4673 | NONE0 | stdlib v1.20.5 fixed in 1.23.10, 1.24.4 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2020-27748 | NONE0 | xdg-utils 1.1.3-4.1 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-29406 | NONE0 | stdlib v1.20.5 fixed in 1.19.11, 1.20.6 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-24785 | NONE0 | stdlib v1.20.5 fixed in 1.21.8, 1.22.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-47906 | NONE0 | stdlib v1.20.5 fixed in 1.23.12, 1.24.6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61727 | NONE0 | stdlib v1.20.5 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.20.5 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56866 | NONE0 | stdlib v1.20.5 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-94439 | NONE0 | stdlib v1.20.5 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-32282 | NONE0 | stdlib v1.20.5 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-39318 | NONE0 | stdlib v1.20.5 fixed in 1.20.8, 1.21.1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-39319 | NONE0 | stdlib v1.20.5 fixed in 1.20.8, 1.21.1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-32289 | NONE0 | stdlib v1.20.5 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94448 | NONE0 | stdlib v1.20.5 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.20.5 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-24783 | NONE0 | stdlib v1.20.5 fixed in 1.21.8, 1.22.1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-24791 | NONE0 | stdlib v1.20.5 fixed in 1.21.12, 1.22.5 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-34155 | NONE0 | stdlib v1.20.5 fixed in 1.22.7, 1.23.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-34158 | NONE0 | stdlib v1.20.5 fixed in 1.22.7, 1.23.1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2024-45336 | NONE0 | stdlib v1.20.5 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97032 | NONE0 | stdlib v1.20.5 fixed in 1.26.9, 1.27.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-15059 | NONE0 | systemd 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15059 | NONE0 | systemd-sysv 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-24789 | NONE0 | stdlib v1.20.5 fixed in 1.21.11, 1.22.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-0913 | NONE0 | stdlib v1.20.5 fixed in 1.23.10, 1.24.4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32288 | NONE0 | stdlib v1.20.5 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-24784 | NONE0 | stdlib v1.20.5 fixed in 1.21.8, 1.22.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-27142 | NONE0 | stdlib v1.20.5 fixed in 1.25.8, 1.26.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-39823 | NONE0 | stdlib v1.20.5 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39826 | NONE0 | stdlib v1.20.5 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-29409 | NONE0 | stdlib v1.20.5 fixed in 1.19.12, 1.20.7, 1.21.0-rc.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-39326 | NONE0 | stdlib v1.20.5 fixed in 1.20.12, 1.21.5 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-45284 | NONE0 | stdlib v1.20.5 fixed in 1.20.11, 1.21.4 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-45289 | NONE0 | stdlib v1.20.5 fixed in 1.21.8, 1.22.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-45290 | NONE0 | stdlib v1.20.5 fixed in 1.21.8, 1.22.1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-22866 | NONE0 | stdlib v1.20.5 fixed in 1.22.12, 1.23.6, 1.24.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22873 | NONE0 | stdlib v1.20.5 fixed in 1.23.9, 1.24.3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-47912 | NONE0 | stdlib v1.20.5 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58185 | NONE0 | stdlib v1.20.5 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58187 | NONE0 | stdlib v1.20.5 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58189 | NONE0 | stdlib v1.20.5 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61723 | NONE0 | stdlib v1.20.5 fixed in 1.24.8, 1.25.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-61724 | NONE0 | stdlib v1.20.5 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61725 | NONE0 | stdlib v1.20.5 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61730 | NONE0 | stdlib v1.20.5 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.20.5 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42507 | NONE0 | stdlib v1.20.5 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-78663 | NONE0 | stdlib v1.20.5 fixed in 1.26.9, 1.27.2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-58186 | NONE0 | stdlib v1.20.5 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-22870 | NONE0 | stdlib v1.20.5 fixed in 1.23.7, 1.24.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-45341 | NONE0 | stdlib v1.20.5 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.6% Theoretical Threat | Not Applicable |
| DLA-4854-1 | NONE0 | tzdata 2026c-0+deb12u1 fixed in 2026e-0+deb12u1 | — | Not Applicable |
| CVE-2023-31437 | NONE0 | systemd 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | systemd 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | systemd 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | systemd-sysv 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | systemd-sysv 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | systemd-sysv 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | systemd 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | systemd 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | systemd-sysv 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | systemd-sysv 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56857 | NONE0 | stdlib v1.20.5 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-52968 | NONE0 | xdg-utils 1.1.3-4.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27139 | NONE0 | stdlib v1.20.5 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.