Defined in 2 files
Last patched
_verify_source_safety in run-llama/llama_index was changed by 3 published CVE fixes between 2023 and 2024, in 3 distinct patches that added or removed 22 lines in total.
The name occurs in 2 files: llama-index-core/llama_index/core/exec_utils.py, llama_index/exec_utils.py.
run-llama/llama_index has 26 CVEs with a located fix in total, so 12% of them touched this function.
Every published CVE whose fix changed _verify_source_safety, newest first, with the lines each fix touched.
CVE-2024-3271 · llama-index-core/llama_index/core/exec_utils.py · lines 144–145 · +2 −1
CVE-2024-3098 · llama-index-core/llama_index/core/exec_utils.py · lines 144–145 · +2 −1
CVE-2023-39662 · llama_index/exec_utils.py · lines 94–109 · +16 −0
Get an alert when the next CVE fix lands in run-llama/llama_index, with the patched functions.
Monitor llama_index CVEsFunctions in the same files that CVE fixes also changed.
Functions in run-llama/llama_index changed by the most CVE fixes.
Common questions about CVE fixes to _verify_source_safety.
Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.
Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.
