gradiant/srsran-5g:23_10_1 container image
Docker HubScanned 30 Sept 2026
Deployed by 2 of 17,966 indexed charts (latest versions) at this tag.Docker Hub all tags of gradiant/srsran-5g
gradiant/srsran-5g:23_10_1 resolved to 9061b1bf0f36, scanned 30 Sept 2026: 7,895 findings, 15 critical, 19 on KEV; deployed by 2 charts, among them srsran-5g and srsran-5g-zmq.
Radar Score
72,78215315667,283
7,895 findings on digest 9061b1bf0f36 · scanned 30 Sept 2026
KEV ×19 confirmed exploitedRadar Score is the sum of every finding’s contribution; the colour is the worst finding’s band.
Vulnerabilities
7,895 distinct on this digest
Findings for digest 9061b1bf0f36 as scanned on 30 Sept 2026 with syft 1.42.1 for linux/amd64, advisories as of 30 Sept 2026. Other architectures may differ.
| Severity | Advisory | Package | Fixed in |
|---|---|---|---|
| Low | UBUNTU-CVE-2022-49119 | linux | no fix listed |
| Low | UBUNTU-CVE-2023-43114 | qtbase-opensource-src | no fix listed |
| Low | UBUNTU-CVE-2024-1151 | linux | no fix listed |
| Low | UBUNTU-CVE-2024-26651 | linux | 5.4.0-189.209 |
| Low | UBUNTU-CVE-2024-40960 | linux | 5.4.0-195.215 |
| Low | UBUNTU-CVE-2024-57901 | linux | 5.4.0-211.231 |
| Low | UBUNTU-CVE-2024-58010 | linux | 5.4.0-216.236 |
| Low | UBUNTU-CVE-2024-57893 | linux | no fix listed |
| Low | UBUNTU-CVE-2022-49219 | linux | no fix listed |
| Low | UBUNTU-CVE-2022-49409 | linux | 5.4.0-192.212 |
| Low | UBUNTU-CVE-2023-52882 | linux | 5.4.0-192.212 |
| Low | UBUNTU-CVE-2024-26937 | linux | 5.4.0-189.209 |
| Low | UBUNTU-CVE-2026-63833 | linux | no fix listed |
| Low | UBUNTU-CVE-2026-93229 | linux | no fix listed |
| Low | UBUNTU-CVE-2022-49072 | linux | 5.4.0-227.247 |
| Low | UBUNTU-CVE-2022-49118 | linux | no fix listed |
| Low | UBUNTU-CVE-2022-49120 | linux | no fix listed |
| Low | UBUNTU-CVE-2022-49121 | linux | no fix listed |
| Low | UBUNTU-CVE-2022-49156 | linux | no fix listed |
| Low | UBUNTU-CVE-2022-49157 | linux | no fix listed |
| Low | UBUNTU-CVE-2022-49188 | linux | no fix listed |
| Low | UBUNTU-CVE-2022-49226 | linux | no fix listed |
| Low | UBUNTU-CVE-2022-49281 | linux | no fix listed |
| Low | UBUNTU-CVE-2022-49294 | linux | no fix listed |
| Low | UBUNTU-CVE-2022-49310 | linux | no fix listed |
| Low | UBUNTU-CVE-2022-49312 | linux | no fix listed |
| Low | UBUNTU-CVE-2022-49376 | linux | no fix listed |
| Low | UBUNTU-CVE-2022-49398 | linux | no fix listed |
| Low | UBUNTU-CVE-2022-49449 | linux | no fix listed |
| Low | UBUNTU-CVE-2022-49497 | linux | no fix listed |
| Low | UBUNTU-CVE-2022-49521 | linux | no fix listed |
| Low | UBUNTU-CVE-2022-49537 | linux | no fix listed |
| Low | UBUNTU-CVE-2024-26642 | linux | 5.4.0-189.209 |
| Low | UBUNTU-CVE-2024-33621 | linux | 5.4.0-192.212 |
| Low | UBUNTU-CVE-2024-40961 | linux | 5.4.0-195.215 |
| Low | UBUNTU-CVE-2024-40979 | linux | no fix listed |
| Low | UBUNTU-CVE-2024-56636 | linux | no fix listed |
| Low | UBUNTU-CVE-2025-37852 | linux | no fix listed |
| Low | UBUNTU-CVE-2022-49046 | linux | 5.4.0-228.248 |
| Low | UBUNTU-CVE-2022-49135 | linux | no fix listed |
| Low | UBUNTU-CVE-2023-52761 | linux | no fix listed |
| Low | UBUNTU-CVE-2024-26993 | linux | 5.4.0-189.209 |
| Low | UBUNTU-CVE-2024-35947 | linux | 5.4.0-192.212 |
| Low | UBUNTU-CVE-2024-50233 | linux | 5.4.0-208.228 |
| Low | UBUNTU-CVE-2024-56705 | linux | no fix listed |
| Low | UBUNTU-CVE-2025-37842 | linux | no fix listed |
| Low | UBUNTU-CVE-2025-37853 | linux | no fix listed |
| Low | UBUNTU-CVE-2026-97496 | linux | no fix listed |
| Low | UBUNTU-CVE-2025-4516 | python3.8 | 3.8.10-0ubuntu1~20.04.18+esm1 |
| Low | UBUNTU-CVE-2022-49108 | linux | no fix listed |