Skepra / Web recovery & resilience

Debian zlib: separate package, service and image decisions.

Debian published DSA-6613-1 on 7 November 2026. An agency maintaining a Debian web service needs a clear maintenance boundary across the host, running services and deployment images.

Discuss the next maintenance decision

What Debian published

DSA-6613-1 covers CVE-2026-27171, CVE-2026-76844 and CVE-2026-85091. Debian describes denial of service or potential code execution when specially crafted input is processed.

Debian package applicability

The Debian tracker marks trixie zlib source version 1:1.3.dfsg+really1.3.1-1 vulnerable and 1:1.3.dfsg+really1.3.1-1+deb13u1 fixed. These are Debian source-package revisions. Have the operator map installed binary packages and their origin before comparing versions; the notice alone does not identify a vulnerable site.

Decision 1: package scope

Record each maintenance unit, distribution, package origin, full revision and named operator. A host installation, a container and a separately bundled library need their own evidence. Unknown lineage calls for inventory and vendor matching, not an assumption that the trixie threshold applies.

Decision 2: running-service activation

Agree which long-lived services need restart assessment, who authorizes disruption, and which application checks will demonstrate an acceptable handoff. Keep this decision open when only package evidence is available. The Debian needrestart manual describes daemon restart assessment after library upgrades; tool output still requires operator interpretation.

Decision 3: deployed images

For each relevant image, record its deployed digest, build owner and package evidence. Agree any rebuild and replacement separately, with an acceptance test and recovery point. A fixed host package row does not close an unresolved image row.

This is a proposed evidence worksheet, not a claim of tested remediation.

Sources and review boundary

Vendor disclosure: 7 November 2026. References checked 8 November. Reachability and actual installation status remain a separate operator assessment.

Review and next decision

Skepra editorial review: 8 November 2026. Recheck the vendor notice before implementation. If scope or ownership is unclear, a Recovery Review can clarify the next route before separately agreed work.

Agencies and MSPs remain client-facing under agreed terms.