βββ ββββββββββββ ββββββββββββββββ βββββββ
βββ ββββββββββββ ββββββββββββββββββββββββ
βββ βββ βββ ββββββββββββββ βββ
ββββ ββββ βββ ββββββββββββββ βββ
βββββββ βββ ββββββββββββββββββββββββ
βββββ βββ ββββββββββββββββ βββββββ
Security Fixes Β· patches for packages the autoupdater forgot
Some packages don't get the security update. - VT Security
A personal, growing collection of security patches for open-source packages that fall through the cracks of automatic updates - the long tail of community-maintained software where a CVE is public, an upstream fix exists, but nothing has landed in the channel most people actually run.
Each fix here is DEP-3 formatted and ready to drop into debian/patches/, with the
provenance (upstream commit, CVE, bug links) baked into the patch header. The focus is
Ubuntu universe CVEs and, since November 2026, Debian stable updates. The
layout is distro-agnostic - anything with a public CVE and an upstream fix is fair game.
| Scope | Open-source security patches (Ubuntu universe and Debian stable) |
| Format | DEP-3 patches, ready for debian/patches/ |
| Status | Tracked in fixes.yaml |
| Contributing | See CONTRIBUTING.md |
Canonical ships automatic security updates for main, but universe packages are community-maintained - they only get fixes if someone does the SRU (Stable Release Update) work. For libsoup3 and YAML::Syck below, fixes already exist in the ESM (Ubuntu Pro) pocket, but the standard pocket - what most users run - is still vulnerable. For gdcm no supported Ubuntu release ships a fix at all. These patches bridge that gap, and are formatted so a maintainer can pick them up with zero rework.
| Severity | HIGH (CVSS 7.5) |
| Issue | Out-of-bounds read in cookie date parsing - integer overflow in parse_timezone() |
| Package | libsoup3 |
| Affected | jammy only (all other releases already patched) |
| ESM status | β
esm-apps/jammy: released (3.0.7-0ubuntu1+esm5) |
| Standard status | β jammy: needed |
| Upstream fix | GNOME MR !473 |
| Debian bug | #1116469 (closed; fixed in unstable 3.6.5-5) |
| Launchpad bug | LP: #2157576 (not publicly visible on 2026-09-29) |
| Patch | libsoup3/CVE-2025-11021-CVE-2025-4945.patch |
Ubuntu attributes both CVEs to MR !473, which is what this patch carries. Debian attributes CVE-2025-11021 to MR !482 (NULL checks in
soup_date_time_to_string()/ cookie serialization) and still lists trixie's 3.6.5-3, which has !473, as vulnerable. Until that is settled, claim this patch for CVE-2025-4945 and for theparse_timezone()part of CVE-2025-11021 only.
- Ubuntu CVE page
- Launchpad package
- CLI:
rmadison libsoup3 \| grep jammy
| Severity | MEDIUM (CVSS 6.5) |
| Issue | Missing null terminators in token.c - out-of-bounds read on empty-key YAML hashes |
| Package | libyaml-syck-perl |
| Affected | jammy, noble |
| ESM status | β
esm-apps/jammy: released (1.34-1ubuntu0.1~esm1), esm-apps/noble: released (1.34-2ubuntu0.24.04.1~esm1) |
| Standard status | β jammy: needed, noble: needed |
| Upstream fix | dcf4c84 (v1.36) |
| Launchpad bug | LP: #2157577 (not publicly visible on 2026-09-29) |
| Patch | libyaml-syck-perl/CVE-2025-11683.patch |
- Ubuntu CVE page
- Launchpad package
- CLI:
rmadison libyaml-syck-perl \| grep -E "jammy\|noble"
| Severity | MEDIUM (CVSS 6.6) |
| Issue | OOB write in DICOM fragment parsing - missing bounds check before buffer access |
| Package | gdcm |
| Affected | jammy, noble (questing reached end of life and is ignored; its debdiff is kept, not submitted) |
| ESM status | none - no Ubuntu pocket carries a fix |
| Standard status | β jammy: needed, noble: needed |
| Upstream fix | 5829c95 (v3.2.2) |
| Debian bug | #1122862 (closed; fixed in unstable 3.0.24-11) |
| Launchpad bug | LP: #2157578 (not publicly visible on 2026-09-29) |
| Patch | gdcm/CVE-2025-11266.patch |
- Ubuntu CVE page
- Launchpad package
- CLI:
rmadison gdcm
Since November 2026 the same method is applied to Debian itself, for packages of the
Debian Med team that read medical image files
and still have open CVEs in the stable release. These updates go through the package
maintainers and a stable point release (trixie-pu), not through an SRU, so they are not
part of fixes.yaml or tools/submit-sru.sh.
State on 2026-11-10. None of these is in the Debian archive yet.
| Package | Target | Issue | Where | State |
|---|---|---|---|---|
gdcm |
unstable | Regression of the CVE-2025-53618 / CVE-2025-53619 patch | #1152837 | Reported with a patch; open |
gdcm |
trixie (13) | CVE-2025-11266, CVE-2025-48429, CVE-2025-52582, CVE-2025-53618, CVE-2025-53619, CVE-2026-3650 | #1153126 | trixie-pu request filed with the debdiff; agreed with the team, waiting for the release team |
gdcm |
bookworm (12, LTS) | The same six CVEs | debian-med list | Debdiff sent on 2026-11-05; a Debian developer is reviewing it |
invesalius |
unstable, then trixie (13) | CVE-2024-44825, plus CVE-2024-42845 in trixie | #1136204 | Patch sent to the bug on 2026-11-10, with test results for it and for the patch already proposed there; open. The trixie debdiff waits for the fix in unstable |
pydicom |
trixie (13) | CVE-2026-32711 | #1131492 | Debdiff from the merged Debian Med trixie branch; Karsten confirmed on 2026-11-16 that his existing trixie-pu request #1148120 awaits release-team approval. The local filing draft is superseded; do not open a duplicate |
Each of these package folders has a debian/ subfolder with the debdiff and the text of
what was sent or is going to be sent: the mail to the team, the bug report or reply, and
the trixie-pu request. A draft says so in its first line.
How an update is prepared:
- Take the CVEs that the Debian security tracker lists as open in stable and that are fixed in unstable or upstream.
- Backport the patch with a DEP-3 header.
- Build in a clean container of the target release.
- Compare the old and the new package, on crafted input and on ordinary files.
- Agree the change with the maintainers before asking the release team.
Read from the live trackers on 2026-09-29. No fix has landed in a standard Ubuntu pocket
since the 2026-09-14 review, and nothing is waiting in -proposed. None of the three
Ubuntu tracker entries changed after 2026-09-14 (last updates: libsoup3 2025-12-11,
YAML::Syck 2025-10-29, gdcm 2026-07-10).
| Fix | Series | Ubuntu tracker | Standard pocket today (Launchpad) | Debian |
|---|---|---|---|---|
| libsoup3 CVE-2025-11021 / CVE-2025-4945 | jammy | released in esm-apps only |
3.0.7-0ubuntu1 (jammy-updates, 2022) |
fixed in sid; bookworm/trixie vulnerable, no-dsa |
| libyaml-syck-perl CVE-2025-11683 | jammy, noble | released in esm-apps only |
1.34-1build2 / 1.34-2build3 (release pocket) |
fixed in bookworm, trixie and sid |
| gdcm CVE-2025-11266 | jammy, noble | needed | 3.0.10-1build2 / 3.0.22-2.1ubuntu1 (release pocket) |
fixed in sid; bookworm/trixie vulnerable, no-dsa |
- The three sponsorship bugs (LP: #2157576, #2157577, #2157578) return 404 when logged out. A private security bug looks the same, so their state can only be checked from the filer's Launchpad account; this review makes no claim that they were accepted.
- The Ubuntu tracker lists YAML::Syck as
neededon resolute, but resolute publishes 1.36-1, which contains the upstream fix. Treated as tracker lag. - libsoup3: Ubuntu and Debian disagree on which upstream change fixes CVE-2025-11021 (see the note in its section).
Sources: the Ubuntu CVE pages linked in each section, the Debian security tracker entries for each CVE, and Launchpad's publishing history for libsoup3, libyaml-syck-perl and gdcm. The previous review (2026-09-14) found the same standard-pocket state and marked gdcm on questing as ignored after its end of life.
- File a Launchpad bug for each CVE at
bugs.launchpad.net/ubuntu/+source/<pkg>(a ready-to-pastebug-report.mdlives in each package folder) - Download source:
pull-lp-source <pkg> jammy - Apply patch: copy
.patchintodebian/patches/, add toseries - Changelog:
dch -v "<version>.1" -D jammy-security "SECURITY UPDATE: ..." - Build & upload:
debuild -S -sa && dput ubuntu ../*.changes
The patches are DEP-3 formatted - they include Origin, Bug links, and upstream commit references. Ready for
debian/patches/.
The merge doesn't happen on GitHub - it happens on Launchpad (Ubuntu's platform). Here's how to track each step:
| What to check | How | Meaning |
|---|---|---|
| CVE tracker status | ubuntu.com/security/cves - search the CVE ID | If it says "Fixed" or shows a released version, the patch shipped |
| Package version | rmadison <pkg> on any Ubuntu machine |
Look for -security or -updates pocket with the patched version |
| Launchpad bug | The bug you filed when submitting | Status goes: New β In Progress β Fix Committed β Fix Released |
| UCT git repo | git clone lp:ubuntu-cve-tracker && grep <pkg> active/CVE-* |
needed changes to released (<version>) |
| USN notice | ubuntu.com/security/notices | Canonical publishes a USN when the fix ships |
# Check if the fix shipped
rmadison libsoup3 | grep jammy-security
# Check the CVE tracker
git clone --depth 1 git://git.launchpad.net/ubuntu-cve-tracker
grep jammy_libsoup3 ubuntu-cve-tracker/active/CVE-2025-11021fixes.yaml β machine-readable index of every fix + its status
CONTRIBUTING.md β how to add a new fix
_template/ β scaffolding for a new package fix
tools/
new-fix.sh β bootstrap a new package folder from the template
verify-patches.sh β sanity-check every patch in the repo
check-readme-sync.py β fail if README.md or submit-sru.sh drift from fixes.yaml
submit-sru.sh β build source-only SRU uploads for every fix (Ubuntu only)
libsoup3/ β CVE-2025-11021 / CVE-2025-4945
libyaml-syck-perl/ β CVE-2025-11683
gdcm/ β CVE-2025-11266; debian/ has the trixie and bookworm updates
invesalius/ β CVE-2024-44825 (Debian only)
pydicom/ β CVE-2026-32711 (Debian only)
Each package folder contains the .patch file, a ready-to-file bug-report.md, and any
packaging diffs (changelog.diff, *.debdiff). The Debian-only folders have no
bug-report.md; their texts are in debian/.
./tools/new-fix.sh <package> <CVE-id> # scaffold from _template/
./tools/verify-patches.sh # DEP-3 headers and hunk line counts only; does not apply or build
./tools/check-readme-sync.py # README tables and submit-sru.sh match fixes.yamlOn an Ubuntu box/schroot for the target series (won't run on Debian), one
script builds source-only uploads for every fix - pull-lp-source, apply patch,
quilt push -a, dch, debuild -S:
./tools/submit-sru.sh # build all, unsigned source packages
./tools/submit-sru.sh --sign # sign with your Launchpad GPG key
./tools/submit-sru.sh --upload # sign + dput ubuntu (irreversible - yours to run)The signing/dput (and filing the Launchpad bug per package) are intentionally
left to you: they're outward-facing and tied to your Launchpad identity.
See CONTRIBUTING.md for the full workflow.
The tooling, templates and documentation in this repository (tools/, _template/,
fixes.yaml, the Markdown files) are licensed under the Apache License 2.0.
The patches and debdiffs under each package directory are derivative works of those
packages and are distributed under the license of the package they modify (see
debian/copyright of each source package). Apache-2.0 does not apply to them.
Maintained by ValentΓn Torassa Β· part of the VT Security toolset Β· companion to PhantomLog and VT-SecretShare