_get_segment_for_document
Defined in 2 files
Last patched
Overview
_get_segment_for_document in langgenius/dify was changed by 1 published CVE fixes in 2026, in 4 distinct patches that added or removed 30 lines in total.
Defined in 2 files
Last patched
_get_segment_for_document in langgenius/dify was changed by 1 published CVE fixes in 2026, in 4 distinct patches that added or removed 30 lines in total.
The name occurs in 2 files: api/controllers/console/datasets/datasets_segments.py, api/controllers/service_api/dataset/segment.py.
langgenius/dify has 20 CVEs with a located fix in total, so 5% of them touched this function.
Every published CVE whose fix changed _get_segment_for_document, newest first, with the lines each fix touched.
CVE-2026-105761 · api/controllers/console/datasets/datasets_segments.py · lines 166–180 · +15 −0
CVE-2026-105761 · api/controllers/service_api/dataset/segment.py · lines 131–145 · +15 −0
Get an alert when the next CVE fix lands in langgenius/dify, with the patched functions.
Monitor dify CVEsFunctions in the same files that CVE fixes also changed.
Functions in langgenius/dify changed by the most CVE fixes.
Common questions about CVE fixes to _get_segment_for_document.
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.