Debian Updates NGINX for HTTP Processing and Client-Certificate Flaws

P2 — VALIDATE AND UPDATENot provided by the authority · Not provided by the authorityEXPLOITATION: NOT STATED

Quick Answer

Update Debian trixie nginx to 1.26.3-3+deb13u11, validate active services and retain package and application-test evidence.

Confirm Scope And Apply The Supported Remediation

What to do now: Identify Debian trixie systems, installed nginx packages, application use, dependent services and responsible owners. Match the installed Debian release and package revision to this advisory; assess application-specific exposure rather than assuming all installations have identical impact. Apply the supported Debian security package update, refresh affected deployment images and restart dependent long-running processes where required. Test configuration, TLS client-certificate enforcement, proxy routing and worker turnover after updating. Retain before-and-after versions, package transactions and test outcomes.

Open the authoritative advisory

Last verified: 2026-11-19 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopenginx on Debian 13 (trixie)
AdvisoryDSA-6642-1
CVEsCVE-2026-113425, CVE-2026-118899, CVE-2026-120967, CVE-2026-121810, CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-123640, CVE-2026-125283
Authoritative release date2026-11-19T14:40:29Z — dated Debian security-announce message.
Authority revision dateNo separate material revision is stated for this release.
Affected versionsDebian 13 (trixie) nginx packages before the corrected 1.26.3-3+deb13u11 build identified by DSA-6642-1.
Fixed versionnginx 1.26.3-3+deb13u11
CVSS base scoreNot provided by the authority
CVSS severityNot provided by the authority
Exploitation statusThe cited authority does not confirm exploitation of these vulnerabilities in the wild.; no exploitation claim is inferred.

What Changed

The NGINX update addresses remote code execution, denial of service, information disclosure and bypass of client-certificate verification.

What To Validate Now

  1. Inventory. Identify Debian trixie systems, installed nginx packages, application use, dependent services and responsible owners.
  2. Establish applicability. Match the installed Debian release and package revision to this advisory; assess application-specific exposure rather than assuming all installations have identical impact.
  3. Remediate. Apply the supported Debian security package update, refresh affected deployment images and restart dependent long-running processes where required.
  4. Validate. Test configuration, TLS client-certificate enforcement, proxy routing and worker turnover after updating. Retain before-and-after versions, package transactions and test outcomes.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Coordinate proxy changes with application owners. Do not replace Debian package-version guidance with upstream version numbers; backported fixes use Debian revisions.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.