Source: qt6-base X-Debbugs-CC: [email protected] Severity: important Tags: security
Hi, The following vulnerabilities were published for qt6-base. All of these are fixed in 6.11.3: CVE-2026-95620[0]: | A use-after-free vulnerability in the Qt QNetworkAccessManager | HTTP/2 client support of the Qt Network module allows a malicious or | compromised HTTP/2 server to cause the client application to crash, | affecting availability. https://wiki.qt.io/List_of_known_vulnerabilities_in_Qt_products#CVE-2026-95620: Fixed by: https://github.com/qt/qtbase/commit/c4ae6491d473e36f34840a236c5fd0f4bc800558 CVE-2026-96432[1]: | A malicious or compromised HTTP/2 server withholding SETTINGS ACK | can send RST_STREAM on a completed stream, planting a null pointer, | and then send a PUSH_PROMISE for that stream, causing a null pointer | dereference in the QNetworkAccessManager class of the Qt Network | module that crashes the application. https://wiki.qt.io/List_of_known_vulnerabilities_in_Qt_products#CVE-2026-96432: Fixed by: https://github.com/qt/qtbase/commit/156dcb4770d7f4747b973ba509f6df1933f64817 (v6.11.3) CVE-2026-105923[2]: | A malicious SVG can trigger an integer overflow which in turn | triggers a null-pointer dereference in VectorImage QML Type. https://codereview.qt-project.org/c/qt/qtbase/+/762279 https://wiki.qt.io/List_of_known_vulnerabilities_in_Qt_products#CVE-2026-105923: Fixed by: https://github.com/qt/qtbase/commit/d2129a7f0e1f2ebef3f4897276db9b5b05874d8f CVE-2026-107157[3]: | Specially crafted CBOR input passed to QCborValue::fromCbor() in Qt | Core can cause an out-of-bounds read, which may crash the | application and could expose information. https://wiki.qt.io/List_of_known_vulnerabilities_in_Qt_products#CVE-2026-107157: https://codereview.qt-project.org/c/qt/qtbase/+/745719 Fixed by: https://github.com/qt/qtbase/commit/08c5ae85586ef9ef6b3f80f98f367de48c6db3d0 (v6.11.3) If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2026-95620 https://www.cve.org/CVERecord?id=CVE-2026-95620 [1] https://security-tracker.debian.org/tracker/CVE-2026-96432 https://www.cve.org/CVERecord?id=CVE-2026-96432 [2] https://security-tracker.debian.org/tracker/CVE-2026-105923 https://www.cve.org/CVERecord?id=CVE-2026-105923 [3] https://security-tracker.debian.org/tracker/CVE-2026-107157 https://www.cve.org/CVERecord?id=CVE-2026-107157 Please adjust the affected versions in the BTS as needed.
