| Message ID | 20260207103359.4177243-14-skandigraun@gmail.com |
|---|---|
| State | New |
| Headers | show |
| Series | [meta-oe,scarthgap,01/15] imagemagick: patch CVE-2025-66628 | expand |
diff --git a/meta-python/recipes-devtools/python/python3-tornado/CVE-2025-67726.patch b/meta-python/recipes-devtools/python/python3-tornado/CVE-2025-67726.patch index 7b210aea42..01f18e3bd9 100644 --- a/meta-python/recipes-devtools/python/python3-tornado/CVE-2025-67726.patch +++ b/meta-python/recipes-devtools/python/python3-tornado/CVE-2025-67726.patch @@ -8,7 +8,7 @@ certain inputs, which could be a DoS vector. This change adapts logic from the equivalent function in the python standard library in https://github.com/python/cpython/pull/136072/files -CVE: CVE-2025-67726 +CVE: CVE-2025-67726 CVE-2025-67725 Upstream-Status: Backport [https://github.com/tornadoweb/tornado/commit/771472cfdaeebc0d89a9cc46e249f8891a6b29cd] (cherry picked from commit 771472cfdaeebc0d89a9cc46e249f8891a6b29cd) Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
Details: https://nvd.nist.gov/vuln/detail/CVE-2025-67725 According to the NVD advisory references the same commit fixes it as CVE-2025-67726. Just extend the CVE tag to make the cve-checker also see this. Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com> --- .../python/python3-tornado/CVE-2025-67726.patch | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)