Debian Package Tracker
Register | Log in
Subscribe

qt6-5compat

Choose email to subscribe with

general
  • source: qt6-5compat (main)
  • version: 6.11.2-2
  • maintainer: Debian Qt/KDE Maintainers (archive) (DMD)
  • uploaders: Patrick Franz [DMD]
  • arch: all any
  • std-ver: 4.7.4
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • oldstable: 6.4.2-1
  • stable: 6.8.2-3
  • testing: 6.11.2-2
  • unstable: 6.11.2-2
versioned links
  • 6.4.2-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 6.8.2-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 6.11.2-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • libqt6core5compat6
  • qml6-module-qt5compat-graphicaleffects
  • qt6-5compat-dev
  • qt6-5compat-doc
  • qt6-5compat-doc-html
  • qt6-5compat-examples
action needed
A new upstream version is available: 6.12.0 high
A new upstream version 6.12.0 is available, you should consider packaging it.
Created: 2026-10-02 Last update: 2026-10-27 19:00
2 security issues in trixie high

There are 2 open security issues in trixie.

1 important issue:
  • CVE-2026-101201: A malformed header in the binary file fed to QBinaryJson::fromBinaryData() can cause undefined behaviour because of out-of-bounds read.
1 issue left for the package maintainer to handle:
  • CVE-2026-9499: (needs triaging) An out-of-bounds read (buffer over-read) vulnerability exists in QTextCodec::codecForName() in Qt. When the function is called with a QByteArray that is not NUL-terminated (for example, one created with QByteArray::fromRawData()), the codec-name matching routine reads past the end of the supplied buffer. In most cases this results in an incorrect text codec being selected; in the worst case, if the over-read reaches unmapped memory, the process crashes (denial of service). The over-read is bounded by the length of the longest codec-name candidate, and the out-of-bounds bytes are only compared internally against Qt's fixed list of codec names, so no data is disclosed to an attacker. Applications that do not pass non-NUL-terminated QByteArrays to QTextCodec::codecForName() are not exposed. The affected code resides in the Qt5Compat module from Qt 6.0.0 onward, and in Qt Core (qtbase) in Qt 4.x and Qt 5.x.

You can find information about how to handle this issue in the security team's documentation.

Created: 2026-07-21 Last update: 2026-10-26 11:30
1 security issue in sid high

There is 1 open security issue in sid.

1 important issue:
  • CVE-2026-101201: A malformed header in the binary file fed to QBinaryJson::fromBinaryData() can cause undefined behaviour because of out-of-bounds read.
Created: 2026-10-26 Last update: 2026-10-26 11:30
1 security issue in forky high

There is 1 open security issue in forky.

1 important issue:
  • CVE-2026-101201: A malformed header in the binary file fed to QBinaryJson::fromBinaryData() can cause undefined behaviour because of out-of-bounds read.
Created: 2026-10-26 Last update: 2026-10-26 11:30
2 security issues in bookworm high

There are 2 open security issues in bookworm.

1 important issue:
  • CVE-2026-101201: A malformed header in the binary file fed to QBinaryJson::fromBinaryData() can cause undefined behaviour because of out-of-bounds read.
1 issue postponed or untriaged:
  • CVE-2026-9499: (postponed; to be fixed through a stable update) An out-of-bounds read (buffer over-read) vulnerability exists in QTextCodec::codecForName() in Qt. When the function is called with a QByteArray that is not NUL-terminated (for example, one created with QByteArray::fromRawData()), the codec-name matching routine reads past the end of the supplied buffer. In most cases this results in an incorrect text codec being selected; in the worst case, if the over-read reaches unmapped memory, the process crashes (denial of service). The over-read is bounded by the length of the longest codec-name candidate, and the out-of-bounds bytes are only compared internally against Qt's fixed list of codec names, so no data is disclosed to an attacker. Applications that do not pass non-NUL-terminated QByteArrays to QTextCodec::codecForName() are not exposed. The affected code resides in the Qt5Compat module from Qt 6.0.0 onward, and in Qt Core (qtbase) in Qt 4.x and Qt 5.x.
Created: 2026-10-26 Last update: 2026-10-26 11:30
news
[rss feed]
  • [2026-10-04] qt6-5compat 6.11.2-2 MIGRATED to testing (Debian testing watch)
  • [2026-09-20] Accepted qt6-5compat 6.11.2-2 (source) into unstable (Patrick Franz)
  • [2026-08-23] Accepted qt6-5compat 6.11.2-1 (source) into experimental (Patrick Franz)
  • [2026-07-31] qt6-5compat 6.10.2-4 MIGRATED to testing (Debian testing watch)
  • [2026-07-26] Accepted qt6-5compat 6.10.2-4 (source) into unstable (Patrick Franz)
  • [2026-07-15] qt6-5compat 6.10.2-3 MIGRATED to testing (Debian testing watch)
  • [2026-05-24] Accepted qt6-5compat 6.10.2-3 (source) into unstable (Patrick Franz)
  • [2026-04-03] qt6-5compat 6.10.2-2 MIGRATED to testing (Debian testing watch)
  • [2026-03-19] Accepted qt6-5compat 6.10.2-2 (source) into unstable (Patrick Franz)
  • [2026-02-07] Accepted qt6-5compat 6.10.2-1 (source) into experimental (Patrick Franz)
  • [2025-11-04] qt6-5compat 6.9.2-3 MIGRATED to testing (Debian testing watch)
  • [2025-10-29] Accepted qt6-5compat 6.9.2-3 (source) into unstable (Patrick Franz)
  • [2025-10-01] qt6-5compat 6.9.2-2 MIGRATED to testing (Debian testing watch)
  • [2025-09-22] Accepted qt6-5compat 6.9.2-2 (source) into unstable (Patrick Franz)
  • [2025-09-13] Accepted qt6-5compat 6.9.2-1 (source) into experimental (Patrick Franz)
  • [2025-08-23] Accepted qt6-5compat 6.9.1-2 (source) into experimental (Patrick Franz)
  • [2025-07-22] Accepted qt6-5compat 6.9.1-1 (source) into experimental (Patrick Franz)
  • [2025-03-14] qt6-5compat 6.8.2-3 MIGRATED to testing (Debian testing watch)
  • [2025-03-01] Accepted qt6-5compat 6.8.2-3 (source) into unstable (Patrick Franz)
  • [2025-02-11] Accepted qt6-5compat 6.8.2-2 (source) into experimental (Patrick Franz)
  • [2025-02-08] Accepted qt6-5compat 6.8.2-1 (source) into experimental (Patrick Franz)
  • [2024-11-16] qt6-5compat 6.7.2-3 MIGRATED to testing (Debian testing watch)
  • [2024-11-10] Accepted qt6-5compat 6.7.2-3 (source) into unstable (Patrick Franz)
  • [2024-10-24] qt6-5compat 6.7.2-2 MIGRATED to testing (Debian testing watch)
  • [2024-10-05] Accepted qt6-5compat 6.7.2-2 (source) into unstable (Patrick Franz)
  • [2024-08-31] Accepted qt6-5compat 6.7.2-1 (source) into experimental (Patrick Franz)
  • [2024-06-20] qt6-5compat 6.6.2-2 MIGRATED to testing (Debian testing watch)
  • [2024-06-06] Accepted qt6-5compat 6.6.2-2 (source) into unstable (Patrick Franz)
  • [2024-02-16] Accepted qt6-5compat 6.6.2-1 (source) into experimental (Patrick Franz)
  • [2023-12-22] Accepted qt6-5compat 6.6.1-2 (source) into experimental (Patrick Franz)
  • 1
  • 2
bugs [bug history graph]
  • all: 0
links
  • homepage
  • lintian
  • buildd: logs, reproducibility, cross
  • popcon
  • browse source code
  • other distros
  • security tracker
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 6.11.2-1

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing