chore(findings): aiml/jupyter/jupyter_gpu_codeserver_proxy
Summary
aiml/jupyter/jupyter_gpu_codeserver_proxy has 443 new findings discovered during continuous monitoring.
Layer: aiml/jupyter/jupyterlab-gpu:4.0.11-cuda12.3 is EOL, please update if possible
Layer: opensource/jupyter/jupyterlab-gpu:4.0.11-cuda12.3 is EOL, please update if possible
Layer: opensource/python:v3.11.9 is EOL, please update if possible
Layer: redhat/ubi/ubi9:9.4 is EOL, please update if possible
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=aiml/jupyter/jupyter_gpu_codeserver_proxy&tag=4.22.0&branch=master
EPSS (Exploit Prediction Scoring System) provides an estimate of the likelihood that a vulnerability will be exploited in the wild.
KEV (Known Exploited Vulnerabilities) indicates whether a vulnerability is actively being exploited according to CISA.
id | source | severity | package | impact | workaround | epss_score | kev |
---|---|---|---|---|---|---|---|
CVE-2023-44487 | Twistlock CVE | High | node-18.17.1 | 0.94379 | true | ||
CVE-2024-39689 | Twistlock CVE | High | certifi-2024.6.2 | 0.21233 | false | ||
CVE-2024-29415 | Twistlock CVE | High | ip-1.1.9 | 0.02845 | false | ||
CVE-2024-29415 | Twistlock CVE | High | ip-2.0.1 | 0.02845 | false | ||
CVE-2021-31535 | Twistlock CVE | Medium | libX11-1.7.0-11.el9 | 0.02601 | false | ||
CVE-2021-31535 | Anchore CVE | High | libX11-common-1.7.0-11.el9 | 0.02601 | false | ||
CVE-2021-31535 | Anchore CVE | High | libX11-xcb-1.7.0-11.el9 | 0.02601 | false | ||
CVE-2021-31535 | Anchore CVE | High | libX11-1.7.0-11.el9 | 0.02601 | false | ||
CVE-2022-2182 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.01439 | false | ||
CVE-2022-2182 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.01439 | false | ||
CVE-2022-2182 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.01439 | false | ||
CVE-2022-2183 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.01060 | false | ||
CVE-2022-2183 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.01060 | false | ||
CVE-2022-2183 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.01060 | false | ||
CVE-2024-39700 | Twistlock CVE | Critical | jupyterlab-4.2.3 | 0.00852 | false | ||
CVE-2024-12905 | Twistlock CVE | High | tar-fs-2.1.1 | Really depends on use. Most uses of tarfs use the packaging aspect. Normally if you use the extracting aspect you are also considering things like file limits already. | patches exist for all major release lines. if still unable to update, use a sandboxed directory or switch to tarstream to parse it yourself. | 0.00697 | false |
CVE-2024-49767 | Twistlock CVE | High | werkzeug-3.0.3 | Assuming the other conditions listed are met, then it is possible to exploit this. | Configure Request.maxcontentlength. | 0.00602 | false |
CVE-2022-1720 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00595 | false | ||
CVE-2022-1720 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00595 | false | ||
CVE-2022-1720 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00595 | false | ||
CVE-2024-37890 | Twistlock CVE | High | ws-8.14.2 | 0.00541 | false | ||
CVE-2022-2845 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00513 | false | ||
CVE-2022-2845 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00513 | false | ||
CVE-2022-2845 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00513 | false | ||
CVE-2024-45590 | Twistlock CVE | High | body-parser-1.19.0 | A malicious actor using a specially crafted payload could flood the server with a large number of requests, resulting in denial of service. More technical details can be found at httpsexpressjs.com20241022securityauditmilestoneachievement.html | 0.00504 | false | |
CVE-2024-52804 | Twistlock CVE | Low | tornado-6.4.1 | 0.00400 | false | ||
CVE-2022-1619 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00387 | false | ||
CVE-2022-1619 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00387 | false | ||
CVE-2022-1619 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00387 | false | ||
CVE-2021-4187 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00354 | false | ||
CVE-2021-4187 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00354 | false | ||
CVE-2021-4187 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00354 | false | ||
CVE-2022-4292 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00322 | false | ||
CVE-2022-4292 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00322 | false | ||
CVE-2022-4292 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00322 | false | ||
CVE-2021-3968 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00310 | false | ||
CVE-2021-3968 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00310 | false | ||
CVE-2021-3968 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00310 | false | ||
CVE-2023-38552 | Twistlock CVE | Medium | node-18.17.1 | 0.00267 | false | ||
CVE-2024-43805 | Twistlock CVE | Medium | notebook-7.2.1 | 0.00259 | false | ||
CVE-2024-43805 | Twistlock CVE | Medium | jupyterlab-4.2.3 | 0.00259 | false | ||
CVE-2022-0529 | Twistlock CVE | Low | unzip-6.0-58.el9_5 | 0.00242 | false | ||
CVE-2022-0529 | Anchore CVE | Low | unzip-6.0-58.el9_5 | 0.00242 | false | ||
CVE-2021-4166 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00224 | false | ||
CVE-2021-4166 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00224 | false | ||
CVE-2021-4166 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00224 | false | ||
CVE-2024-12797 | Twistlock CVE | Low | cryptography-42.0.8 | 0.00222 | false | ||
CVE-2024-28849 | Twistlock CVE | Medium | follow-redirects-1.15.4 | 0.00216 | false | ||
CVE-2021-4173 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00206 | false | ||
CVE-2021-4173 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00206 | false | ||
CVE-2021-4173 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00206 | false | ||
CVE-2024-28863 | Twistlock CVE | Medium | tar-6.2.0 | 0.00205 | false | ||
CVE-2021-3974 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00195 | false | ||
CVE-2021-3974 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00195 | false | ||
CVE-2021-3974 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00195 | false | ||
CVE-2022-3705 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00194 | false | ||
CVE-2022-3705 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00194 | false | ||
CVE-2022-3705 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00194 | false | ||
CVE-2022-41723 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00188 | false | ||
CVE-2022-41723 | Anchore CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00188 | false | ||
CVE-2021-3973 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00188 | false | ||
CVE-2021-3973 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00188 | false | ||
CVE-2021-3973 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00188 | false | ||
CVE-2022-0213 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00187 | false | ||
CVE-2022-0213 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00187 | false | ||
CVE-2022-0213 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00187 | false | ||
CVE-2024-22667 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00179 | false | ||
CVE-2024-22667 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00179 | false | ||
CVE-2024-22667 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00179 | false | ||
CVE-2022-2285 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00171 | false | ||
CVE-2022-2285 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00171 | false | ||
CVE-2022-2285 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00171 | false | ||
CVE-2024-45296 | Twistlock CVE | High | path-to-regexp-0.1.7 | Its unlikely you are using routes that match the required characteristics, overwhelming majority of user paths stick with foobar or foo.bar. | Provide a manual regular expression to the second parameter that does not match the prefixed text. | 0.00167 | false |
CVE-2022-2284 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00164 | false | ||
CVE-2022-2284 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00164 | false | ||
CVE-2022-2284 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00164 | false | ||
CVE-2021-3927 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00160 | false | ||
CVE-2021-3927 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00160 | false | ||
CVE-2021-3927 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00160 | false | ||
CVE-2022-2286 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00154 | false | ||
CVE-2022-2286 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00154 | false | ||
CVE-2022-2286 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00154 | false | ||
CVE-2021-4136 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00154 | false | ||
CVE-2021-4136 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00154 | false | ||
CVE-2021-4136 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00154 | false | ||
CVE-2022-2125 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00153 | false | ||
CVE-2022-2125 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00153 | false | ||
CVE-2022-2125 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00153 | false | ||
CVE-2021-4217 | Twistlock CVE | Low | unzip-6.0-58.el9_5 | 0.00148 | false | ||
CVE-2021-4217 | Anchore CVE | Low | unzip-6.0-58.el9_5 | 0.00148 | false | ||
CVE-2024-4068 | Twistlock CVE | High | braces-3.0.2 | 0.00143 | false | ||
CVE-2025-47273 | Twistlock CVE | High | setuptools-70.0.0 | 0.00139 | false | ||
CVE-2022-4293 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00133 | false | ||
CVE-2022-4293 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00133 | false | ||
CVE-2022-4293 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00133 | false | ||
CVE-2022-2042 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00122 | false | ||
CVE-2022-2042 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00122 | false | ||
CVE-2022-2042 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00122 | false | ||
CVE-2022-0530 | Twistlock CVE | Low | unzip-6.0-58.el9_5 | 0.00120 | false | ||
CVE-2022-0530 | Anchore CVE | Low | unzip-6.0-58.el9_5 | 0.00120 | false | ||
CVE-2025-47287 | Twistlock CVE | High | tornado-6.4.1 | 0.00118 | false | ||
CVE-2022-2257 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00114 | false | ||
CVE-2022-2257 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00114 | false | ||
CVE-2022-2257 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00114 | false | ||
CVE-2022-2210 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00114 | false | ||
CVE-2022-2210 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00114 | false | ||
CVE-2022-2210 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00114 | false | ||
CVE-2022-2207 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00114 | false | ||
CVE-2022-2207 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00114 | false | ||
CVE-2022-2207 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00114 | false | ||
CVE-2022-1674 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00113 | false | ||
CVE-2022-1674 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00113 | false | ||
CVE-2022-1674 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00113 | false | ||
CVE-2025-1215 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00112 | false | ||
CVE-2025-1215 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00112 | false | ||
CVE-2025-1215 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00112 | false | ||
CVE-2023-29409 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00112 | false | ||
CVE-2023-29409 | Anchore CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00112 | false | ||
CVE-2025-48387 | Twistlock CVE | High | tar-fs-2.1.1 | If you are extracting untrusted tarballs you are affected and should upgrade. | Patch releases out for ALL release lines, so just update to latest patch, likely your npm already does this, you might need to bump your lock file if you use that. | 0.00110 | false |
CVE-2022-2206 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00108 | false | ||
CVE-2022-2206 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00108 | false | ||
CVE-2022-2206 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00108 | false | ||
CVE-2022-2175 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00108 | false | ||
CVE-2022-2175 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00108 | false | ||
CVE-2022-2175 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00108 | false | ||
CVE-2024-4067 | Twistlock CVE | Medium | micromatch-4.0.5 | 0.00105 | false | ||
CVE-2024-45306 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00104 | false | ||
CVE-2024-45306 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00104 | false | ||
CVE-2024-45306 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00104 | false | ||
CVE-2022-2129 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00101 | false | ||
CVE-2022-2129 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00101 | false | ||
CVE-2022-2129 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00101 | false | ||
CVE-2022-2124 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00098 | false | ||
CVE-2022-2124 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00098 | false | ||
CVE-2022-2124 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00098 | false | ||
CVE-2022-2126 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00097 | false | ||
CVE-2022-2126 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00097 | false | ||
CVE-2022-2126 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00097 | false | ||
CVE-2022-2343 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00090 | false | ||
CVE-2022-2343 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00090 | false | ||
CVE-2022-2343 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00090 | false | ||
CVE-2023-48706 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00088 | false | ||
CVE-2023-48706 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00088 | false | ||
CVE-2023-48706 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00088 | false | ||
CVE-2022-1616 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00088 | false | ||
CVE-2022-1616 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00088 | false | ||
CVE-2022-1616 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00088 | false | ||
CVE-2022-2862 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00084 | false | ||
CVE-2022-2862 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00084 | false | ||
CVE-2022-2862 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00084 | false | ||
CVE-2024-43800 | Twistlock CVE | Medium | serve-static-1.14.1 | Users who are already validating and sanitizing their inputs as expected are highly unlikely to be impacted. | Validate and sanitize user input before passing it to this method. | 0.00073 | false |
CVE-2025-29768 | Twistlock CVE | Medium | vim-8.2.2637-22.el9_6 | 0.00072 | false | ||
CVE-2025-29768 | Anchore CVE | Medium | vim-common-2:8.2.2637-22.el9_6 | 0.00072 | false | ||
CVE-2025-29768 | Anchore CVE | Medium | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00072 | false | ||
CVE-2024-47764 | Twistlock CVE | Low | cookie-0.4.0 | 0.00069 | false | ||
CVE-2024-47764 | Twistlock CVE | Low | cookie-0.4.1 | 0.00069 | false | ||
CVE-2022-1620 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00068 | false | ||
CVE-2022-1620 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00068 | false | ||
CVE-2022-1620 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00068 | false | ||
CVE-2024-52798 | Twistlock CVE | High | path-to-regexp-0.1.7 | 0.00067 | false | ||
CVE-2023-24536 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00066 | false | ||
CVE-2023-24536 | Anchore CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00066 | false | ||
CVE-2024-22019 | Twistlock CVE | High | node-18.17.1 | 0.00064 | false | ||
CVE-2024-43799 | Twistlock CVE | Medium | send-0.17.1 | Application owners have always been expected to sanitize and validate their inputs, so using it correctly should result in very low likelihood of impact. | Validate and sanitize user inputs. | 0.00063 | false |
CVE-2024-49766 | Twistlock CVE | Medium | werkzeug-3.0.3 | Assuming the other conditions listed are met, this is exploitable. | 0.00062 | false | |
CVE-2023-5344 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00062 | false | ||
CVE-2023-5344 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00062 | false | ||
CVE-2023-5344 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00062 | false | ||
CVE-2022-2208 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00062 | false | ||
CVE-2022-2208 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00062 | false | ||
CVE-2022-2208 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00062 | false | ||
CVE-2022-2304 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00058 | false | ||
CVE-2022-2304 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00058 | false | ||
CVE-2022-2304 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00058 | false | ||
CVE-2025-43859 | Twistlock CVE | Critical | h11-0.14.0 | 0.00056 | false | ||
CVE-2022-3297 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00056 | false | ||
CVE-2022-3297 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00056 | false | ||
CVE-2022-3297 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00056 | false | ||
CVE-2021-3928 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00056 | false | ||
CVE-2021-3928 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00056 | false | ||
CVE-2021-3928 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00056 | false | ||
CVE-2022-3256 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00054 | false | ||
CVE-2022-3256 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00054 | false | ||
CVE-2022-3256 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00054 | false | ||
CVE-2023-48237 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00053 | false | ||
CVE-2023-48237 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00053 | false | ||
CVE-2023-48237 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00053 | false | ||
CVE-2023-48233 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00053 | false | ||
CVE-2023-48233 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00053 | false | ||
CVE-2023-48233 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00053 | false | ||
CVE-2023-48232 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00053 | false | ||
CVE-2023-48232 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00053 | false | ||
CVE-2023-48232 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00053 | false | ||
CVE-2023-48231 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00052 | false | ||
CVE-2023-48231 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00052 | false | ||
CVE-2023-48231 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00052 | false | ||
CVE-2022-3296 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00052 | false | ||
CVE-2022-3296 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00052 | false | ||
CVE-2022-3296 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00052 | false | ||
CVE-2022-3234 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00052 | false | ||
CVE-2022-3234 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00052 | false | ||
CVE-2022-3234 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00052 | false | ||
CVE-2023-1170 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00051 | false | ||
CVE-2023-1170 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00051 | false | ||
CVE-2023-1170 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00051 | false | ||
CVE-2022-41725 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00051 | false | ||
CVE-2022-41725 | Anchore CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00051 | false | ||
CVE-2022-2817 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00051 | false | ||
CVE-2022-2817 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00051 | false | ||
CVE-2022-2817 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00051 | false | ||
CVE-2022-1725 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00051 | false | ||
CVE-2022-1725 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00051 | false | ||
CVE-2022-1725 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00051 | false | ||
CVE-2025-27789 | Twistlock CVE | Medium | @babel/runtime-7.23.2 | Its only if you are passing untrusted inputs to the second argument of RegExp.prototype.replace, which is a rare thing to do | 0.00050 | false | |
CVE-2024-43802 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00050 | false | ||
CVE-2024-43802 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00050 | false | ||
CVE-2024-43802 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00050 | false | ||
CVE-2022-2287 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00050 | false | ||
CVE-2022-2287 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00050 | false | ||
CVE-2022-2287 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00050 | false | ||
CVE-2022-3235 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00049 | false | ||
CVE-2022-3235 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00049 | false | ||
CVE-2022-3235 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00049 | false | ||
CVE-2025-47269 | Twistlock CVE | High | code-server-4.22.0 | 0.00048 | false | ||
CVE-2025-24014 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00047 | false | ||
CVE-2025-24014 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00047 | false | ||
CVE-2025-24014 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00047 | false | ||
CVE-2022-2982 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00046 | false | ||
CVE-2022-2982 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00046 | false | ||
CVE-2022-2982 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00046 | false | ||
CVE-2023-4751 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00045 | false | ||
CVE-2023-4751 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00045 | false | ||
CVE-2023-4751 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00045 | false | ||
CVE-2023-24534 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00045 | false | ||
CVE-2023-24534 | Anchore CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00045 | false | ||
CVE-2022-3324 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00045 | false | ||
CVE-2022-3324 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00045 | false | ||
CVE-2022-3324 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00045 | false | ||
CVE-2024-56326 | Twistlock CVE | Medium | jinja2-3.1.4 | This vulnerability impacts applications which execute untrusted templates. This is uncommon for web and other document rendering use cases, but may be common in deployment tools that allow third party plugins. | 0.00044 | false | |
CVE-2023-48235 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00044 | false | ||
CVE-2023-48235 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00044 | false | ||
CVE-2023-48235 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00044 | false | ||
CVE-2022-3037 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00044 | false | ||
CVE-2022-3037 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00044 | false | ||
CVE-2022-3037 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00044 | false | ||
CVE-2024-29041 | Twistlock CVE | Medium | express-5.0.0-alpha.8 | When a user of Express performs a redirect using a userprovided URL Express performs an encode using encodeurl on the contents before passing it to the location header. This can cause malformed URLs to be evaluated in unexpected ways by common redirect allow list implementations in Express applications, leading to an Open Redirect via bypass of a properly implemented allow list.The main method impacted is res.location but this is also called from within res.redirect. | The fix for this involves preparsing the url string with either requirenodeurl.parse or new URL. These are steps you can take on your own before passing the user input string to res.location or res.redirect.More details httpsgithub.comexpressjsexpresssecurityadvisoriesGHSArv95896hc2vc | 0.00043 | false |
CVE-2022-3099 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00043 | false | ||
CVE-2022-3099 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00043 | false | ||
CVE-2022-3099 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00043 | false | ||
CVE-2025-27516 | Twistlock CVE | Medium | jinja2-3.1.4 | This vulnerability impacts applications which execute untrusted templates. This is uncommon for web and other document rendering use cases, but may be common in deployment tools that allow third party plugins. | 0.00042 | false | |
CVE-2024-45336 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00041 | false | ||
CVE-2024-45336 | Anchore CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00041 | false | ||
CVE-2023-4738 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00041 | false | ||
CVE-2023-4738 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00041 | false | ||
CVE-2023-4738 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00041 | false | ||
CVE-2022-3016 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00041 | false | ||
CVE-2022-3016 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00041 | false | ||
CVE-2022-3016 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00041 | false | ||
CVE-2022-2980 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00041 | false | ||
CVE-2022-2980 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00041 | false | ||
CVE-2022-2980 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00041 | false | ||
CVE-2022-2889 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00041 | false | ||
CVE-2022-2889 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00041 | false | ||
CVE-2022-2889 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00041 | false | ||
CVE-2023-48236 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00039 | false | ||
CVE-2023-48236 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00039 | false | ||
CVE-2023-48236 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00039 | false | ||
CVE-2023-48234 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00039 | false | ||
CVE-2023-48234 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00039 | false | ||
CVE-2023-48234 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00039 | false | ||
CVE-2022-2946 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00039 | false | ||
CVE-2022-2946 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00039 | false | ||
CVE-2022-2946 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00039 | false | ||
CVE-2022-3278 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00038 | false | ||
CVE-2022-3278 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00038 | false | ||
CVE-2022-3278 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00038 | false | ||
CVE-2022-2849 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00038 | false | ||
CVE-2022-2849 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00038 | false | ||
CVE-2022-2849 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00038 | false | ||
CVE-2022-2819 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00037 | false | ||
CVE-2022-2819 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00037 | false | ||
CVE-2022-2819 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00037 | false | ||
CVE-2022-2522 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00037 | false | ||
CVE-2022-2522 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00037 | false | ||
CVE-2022-2522 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00037 | false | ||
CVE-2024-8244 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00036 | false | ||
CVE-2024-8244 | Anchore CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00036 | false | ||
CVE-2023-4734 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00036 | false | ||
CVE-2023-4734 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00036 | false | ||
CVE-2023-4734 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00036 | false | ||
CVE-2022-3153 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00036 | false | ||
CVE-2022-3153 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00036 | false | ||
CVE-2022-3153 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00036 | false | ||
CVE-2022-2874 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00036 | false | ||
CVE-2022-2874 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00036 | false | ||
CVE-2022-2874 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00036 | false | ||
CVE-2022-2345 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00036 | false | ||
CVE-2022-2345 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00036 | false | ||
CVE-2022-2345 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00036 | false | ||
CVE-2022-2344 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00036 | false | ||
CVE-2022-2344 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00036 | false | ||
CVE-2022-2344 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00036 | false | ||
CVE-2025-26603 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00033 | false | ||
CVE-2025-26603 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00033 | false | ||
CVE-2025-26603 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00033 | false | ||
CVE-2023-1127 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00033 | false | ||
CVE-2023-1127 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00033 | false | ||
CVE-2023-1127 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00033 | false | ||
CVE-2022-3134 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00033 | false | ||
CVE-2022-3134 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00033 | false | ||
CVE-2022-3134 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00033 | false | ||
CVE-2022-0351 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00033 | false | ||
CVE-2022-0351 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00033 | false | ||
CVE-2022-0351 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00033 | false | ||
CVE-2024-45341 | Twistlock CVE | Low | git-lfs-3.6.1-2.el9_6 | 0.00032 | false | ||
CVE-2024-45341 | Anchore CVE | Low | git-lfs-3.6.1-2.el9_6 | 0.00032 | false | ||
CVE-2023-4781 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00031 | false | ||
CVE-2023-4781 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00031 | false | ||
CVE-2023-4781 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00031 | false | ||
CVE-2023-0288 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00030 | false | ||
CVE-2023-0288 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00030 | false | ||
CVE-2023-0288 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00030 | false | ||
CVE-2022-4141 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00030 | false | ||
CVE-2022-4141 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00030 | false | ||
CVE-2022-4141 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00030 | false | ||
CVE-2025-7039 | Twistlock CVE | Low | glib2-2.68.4-16.el9_6.2 | 0.00029 | false | ||
CVE-2024-47081 | Twistlock CVE | Medium | requests-2.32.3 | 0.00028 | false | ||
CVE-2023-4735 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00027 | false | ||
CVE-2023-4735 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00027 | false | ||
CVE-2023-4735 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00027 | false | ||
CVE-2025-4565 | Twistlock CVE | High | protobuf-5.27.1 | 0.00025 | false | ||
CVE-2024-43374 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00025 | false | ||
CVE-2024-43374 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00025 | false | ||
CVE-2024-43374 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00025 | false | ||
CVE-2025-8941 | Anchore CVE | High | pam-1.5.1-26.el9_6 | 0.00024 | false | ||
CVE-2025-22134 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00023 | false | ||
CVE-2025-22134 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00023 | false | ||
CVE-2025-22134 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00023 | false | ||
CVE-2023-5535 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00023 | false | ||
CVE-2023-5535 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00023 | false | ||
CVE-2023-5535 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00023 | false | ||
CVE-2025-5889 | Twistlock CVE | Low | brace-expansion-1.1.11 | Im mirroring the CVE severity assessment here. | Sanitize strings being passed to the function so that they dont contain many , in a row. | 0.00022 | false |
CVE-2025-5889 | Twistlock CVE | Low | brace-expansion-2.0.1 | Im mirroring the CVE severity assessment here. | Sanitize strings being passed to the function so that they dont contain many , in a row. | 0.00022 | false |
CVE-2023-1175 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00022 | false | ||
CVE-2023-1175 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00022 | false | ||
CVE-2023-1175 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00022 | false | ||
CVE-2024-56201 | Twistlock CVE | Medium | jinja2-3.1.4 | This vulnerability impacts applications which execute untrusted templates where the template author can also choose the template filename. This is uncommon for web and other document rendering use cases, but may be common in deployment tools that allow third party plugins. | Check if any template filenames contain curly braces and . If so, and the braces enclose Python code, audit or remove those files. | 0.00021 | false |
CVE-2022-3352 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00021 | false | ||
CVE-2022-3352 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00021 | false | ||
CVE-2022-3352 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00021 | false | ||
CVE-2022-23806 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00020 | false | ||
CVE-2021-3782 | Anchore CVE | Medium | libwayland-server-1.21.0-1.el9 | 0.00020 | false | ||
CVE-2025-4673 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00019 | false | ||
CVE-2025-4673 | Anchore CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00019 | false | ||
CVE-2023-5441 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00019 | false | ||
CVE-2023-5441 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00019 | false | ||
CVE-2023-5441 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00019 | false | ||
CVE-2023-1264 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00019 | false | ||
CVE-2023-1264 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00019 | false | ||
CVE-2023-1264 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00019 | false | ||
CVE-2022-2923 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00019 | false | ||
CVE-2022-2923 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00019 | false | ||
CVE-2022-2923 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00019 | false | ||
CVE-2023-0051 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00018 | false | ||
CVE-2023-0051 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00018 | false | ||
CVE-2023-0051 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00018 | false | ||
CVE-2024-41965 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00017 | false | ||
CVE-2024-41965 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00017 | false | ||
CVE-2024-41965 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00017 | false | ||
CVE-2023-0049 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00017 | false | ||
CVE-2023-0049 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00017 | false | ||
CVE-2023-0049 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00017 | false | ||
CVE-2025-53906 | Twistlock CVE | Medium | vim-8.2.2637-22.el9_6 | 0.00016 | false | ||
CVE-2025-53906 | Anchore CVE | Medium | vim-common-2:8.2.2637-22.el9_6 | 0.00016 | false | ||
CVE-2025-53906 | Anchore CVE | Medium | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00016 | false | ||
CVE-2025-53905 | Twistlock CVE | Medium | vim-8.2.2637-22.el9_6 | 0.00016 | false | ||
CVE-2025-53905 | Anchore CVE | Medium | vim-common-2:8.2.2637-22.el9_6 | 0.00016 | false | ||
CVE-2025-53905 | Anchore CVE | Medium | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00016 | false | ||
CVE-2024-41957 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00016 | false | ||
CVE-2024-41957 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00016 | false | ||
CVE-2024-41957 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00016 | false | ||
CVE-2023-0433 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00016 | false | ||
CVE-2023-0433 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00016 | false | ||
CVE-2023-0433 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00016 | false | ||
CVE-2023-0054 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00016 | false | ||
CVE-2023-0054 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00016 | false | ||
CVE-2023-0054 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00016 | false | ||
CVE-2022-41724 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00016 | false | ||
CVE-2022-41724 | Anchore CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00016 | false | ||
CVE-2025-50181 | Twistlock CVE | Medium | urllib3-2.2.1 | Most users dont disable redirects on the PoolManager. | Set redirectsFalseredirects0 on the .request call instead of on the toplevel urllib3.PoolManager | 0.00015 | false |
CVE-2025-22870 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00015 | false | ||
CVE-2025-22870 | Anchore CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00015 | false | ||
CVE-2024-47814 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00015 | false | ||
CVE-2024-47814 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00015 | false | ||
CVE-2024-47814 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00015 | false | ||
CVE-2025-9390 | Twistlock CVE | Medium | vim-8.2.2637-22.el9_6 | 0.00014 | false | ||
CVE-2025-9390 | Anchore CVE | Medium | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00014 | false | ||
CVE-2025-9390 | Anchore CVE | Medium | vim-common-2:8.2.2637-22.el9_6 | 0.00014 | false | ||
CVE-2025-30167 | Twistlock CVE | High | jupyter_core-5.7.2 | 0.00014 | false | ||
CVE-2023-2610 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00014 | false | ||
CVE-2023-2610 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00014 | false | ||
CVE-2023-2610 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00014 | false | ||
CVE-2025-50182 | Twistlock CVE | Medium | urllib3-2.2.1 | Pyodide is extremely rare configuration for users in production. | 0.00013 | false | |
CVE-2023-46246 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00013 | false | ||
CVE-2023-46246 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00013 | false | ||
CVE-2023-46246 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00013 | false | ||
CVE-2023-0512 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00013 | false | ||
CVE-2023-0512 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00013 | false | ||
CVE-2023-0512 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00013 | false | ||
CVE-2025-22866 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00012 | false | ||
CVE-2025-22866 | Anchore CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00012 | false | ||
CVE-2023-2609 | Twistlock CVE | Low | vim-8.2.2637-22.el9_6 | 0.00012 | false | ||
CVE-2023-2609 | Anchore CVE | Low | vim-enhanced-2:8.2.2637-22.el9_6 | 0.00012 | false | ||
CVE-2023-2609 | Anchore CVE | Low | vim-common-2:8.2.2637-22.el9_6 | 0.00012 | false | ||
CVE-2025-7339 | Twistlock CVE | Low | on-headers-1.0.2 | 0.00006 | false | ||
CVE-2022-3555 | Anchore CVE | Low | libX11-common-1.7.0-11.el9 | N/A | false | ||
CVE-2022-3555 | Anchore CVE | Low | libX11-1.7.0-11.el9 | N/A | false | ||
CVE-2022-3555 | Anchore CVE | Low | libX11-xcb-1.7.0-11.el9 | N/A | false | ||
CVE-2022-3554 | Anchore CVE | Medium | libX11-common-1.7.0-11.el9 | N/A | false | ||
CVE-2022-3554 | Anchore CVE | Medium | libX11-1.7.0-11.el9 | N/A | false | ||
CVE-2022-3554 | Anchore CVE | Medium | libX11-xcb-1.7.0-11.el9 | N/A | false | ||
GHSA-vqfr-h8mv-ghfj | Anchore CVE | Critical | h11-0.14.0 | N/A | N/A | ||
GHSA-v6h2-p8h4-qcjw | Anchore CVE | Low | brace-expansion-2.0.1 | N/A | N/A | ||
GHSA-q34m-jh98-gwm2 | Anchore CVE | Medium | werkzeug-3.0.3 | N/A | N/A | ||
GHSA-q2x7-8rv6-6q7h | Anchore CVE | Medium | jinja2-3.1.4 | N/A | N/A | ||
GHSA-pq67-6m6q-mj2v | Anchore CVE | Medium | urllib3-2.2.1 | N/A | N/A | ||
GHSA-h4gh-qq45-vh27 | Twistlock CVE | Medium | cryptography-42.0.8 | N/A | N/A | ||
GHSA-h4gh-qq45-vh27 | Anchore CVE | Medium | cryptography-42.0.8 | N/A | N/A | ||
GHSA-gmj6-6f8f-6699 | Anchore CVE | Medium | jinja2-3.1.4 | N/A | N/A | ||
GHSA-f9vj-2wh5-fj8j | Anchore CVE | Medium | werkzeug-3.0.3 | N/A | N/A | ||
GHSA-cpwx-vrp4-4pq7 | Anchore CVE | Medium | jinja2-3.1.4 | N/A | N/A | ||
GHSA-9q39-rmj3-p4r2 | Anchore CVE | High | notebook-7.2.1 | N/A | N/A | ||
GHSA-9q39-rmj3-p4r2 | Anchore CVE | High | jupyterlab-4.2.3 | N/A | N/A | ||
GHSA-9hjg-9r4m-mvj7 | Anchore CVE | Medium | requests-2.32.3 | N/A | N/A | ||
GHSA-8w49-h785-mj3c | Anchore CVE | High | tornado-6.4.1 | N/A | N/A | ||
GHSA-8qvm-5x2c-j2w7 | Anchore CVE | High | protobuf-5.27.1 | N/A | N/A | ||
GHSA-7cx3-6m66-7c5m | Anchore CVE | High | tornado-6.4.1 | N/A | N/A | ||
GHSA-79v4-65xg-pq4g | Anchore CVE | Low | cryptography-42.0.8 | N/A | N/A | ||
GHSA-5rjg-fvgr-3xxf | Anchore CVE | High | setuptools-70.0.0 | N/A | N/A | ||
GHSA-48p4-8xcf-vxj5 | Anchore CVE | Medium | urllib3-2.2.1 | N/A | N/A | ||
GHSA-34jh-p97f-mpxf | Anchore CVE | Medium | urllib3-2.2.1 | N/A | N/A | ||
GHSA-33p9-3p43-82vq | Anchore CVE | High | jupyter-core-5.7.2 | N/A | N/A | ||
GHSA-248v-346w-9cwc | Anchore CVE | Low | certifi-2024.6.2 | N/A | N/A |
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=aiml/jupyter/jupyter_gpu_codeserver_proxy&tag=4.22.0&branch=master
Tasks
Contributor:
-
Provide justifications for findings in the VAT (docs) -
Apply the StatusVerification label to this issue and wait for feedback
Iron Bank:
-
Review findings and justifications
Note: If the above process is rejected for any reason, the
Verification
label will be removed and the issue will be sent back toOpen
. Any comments will be listed in this issue for you to address. Once they have been addressed, you must re-add theVerification
label.
Questions?
Contact the Iron Bank team by commenting on this issue with your questions or concerns. If you do not receive a response, add /cc @ironbank-notifications/onboarding
.
Additionally, Iron Bank hosts an AMA working session every Wednesday from 1630-1730EST to answer questions.