Marked for autoremoval on 19 December due to debugpy: #1145330high
Version 3.44.15+dfsg-1 of qgis is marked for autoremoval from testing on Sat 19 Dec 2026. It depends (transitively) on debugpy, affected by #1145330. You should try to prevent the removal by fixing these RC bugs.
CVE-2026-104140:
QGIS is a free, open source, cross-platform geographic information system. Prior to 3.44.12 and 4.0.0 through 4.2.3, QGIS Server renders feature data in WFS3 (OGC API Features) HTML responses without HTML escaping. Attacker-controlled feature.properties values from a published writable vector layer reach resources/server/api/ogc/templates/wfs3/getFeatures.html through QgsServerOgcApiHandler::htmlDump and the if_nullptr_null_str callback. A user who opens an items HTML page can execute stored markup or script in the QGIS Server origin, which can expose the viewer's session data or issue authenticated requests with the viewer's privileges. This issue is fixed in version 3.44.12.
CVE-2026-104140:
QGIS is a free, open source, cross-platform geographic information system. Prior to 3.44.12 and 4.0.0 through 4.2.3, QGIS Server renders feature data in WFS3 (OGC API Features) HTML responses without HTML escaping. Attacker-controlled feature.properties values from a published writable vector layer reach resources/server/api/ogc/templates/wfs3/getFeatures.html through QgsServerOgcApiHandler::htmlDump and the if_nullptr_null_str callback. A user who opens an items HTML page can execute stored markup or script in the QGIS Server origin, which can expose the viewer's session data or issue authenticated requests with the viewer's privileges. This issue is fixed in version 3.44.12.
vcswatch reports that
this package seems to have a new changelog entry (version
3.44.16+dfsg-1, distribution
unstable) and new commits
in its VCS. You should consider whether it's time to make
an upload.
Lintian reports
3 warnings
about this package. You should make the package lintian clean getting rid of them.
testing migrations
This package will soon be part of the auto-protobuf transition. You might want to ensure that your package is ready for it.
You can probably find supplementary information in the
debian-release
archives or in the corresponding
release.debian.org
bug.