Debian Trixie Moves Thunderbird to the Patched 153.7 ESR Package

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

Quick Answer

Deploy thunderbird 1:153.7.0esr-1~deb13u1 from the trixie security repository and relaunch the application. Test mail, calendar, authentication and required add-ons before broad deployment.

Confirm Scope And Apply The Supported Remediation

What to do now: Identify Debian suite, thunderbird package version and origin, responsible owners, deployment policy and relevant service or user exposure. Match Debian 13 trixie and package origin to the advisory. Assess other suites or upstream installations against their own supported security guidance. Apply thunderbird 1:153.7.0esr-1~deb13u1 through the Debian security repository using the approved maintenance process. Confirm the full installed package version including its epoch, and the running application version after relaunch. Retain rollout records and results for representative mail and calendar workflows.

Open the authoritative advisory

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

Scope And Authority

Product scopethunderbird packages on Debian 13 trixie
AdvisoryDSA-6621-1
CVEsCVE-2026-118007, CVE-2026-118019, CVE-2026-118021, CVE-2026-118024, CVE-2026-124853, CVE-2026-124854, CVE-2026-124855, CVE-2026-124856, CVE-2026-124857, CVE-2026-124858, CVE-2026-124859, CVE-2026-124860, CVE-2026-124861, CVE-2026-124862, CVE-2026-124863, CVE-2026-124864, CVE-2026-124865, CVE-2026-124866, CVE-2026-124868, CVE-2026-124869, CVE-2026-124870, CVE-2026-124872, CVE-2026-124873, CVE-2026-124874, CVE-2026-124875, CVE-2026-124876, CVE-2026-124877, CVE-2026-124879, CVE-2026-124880, CVE-2026-124881, CVE-2026-124882, CVE-2026-124883, CVE-2026-124884, CVE-2026-124885, CVE-2026-124886, CVE-2026-124887, CVE-2026-124888, CVE-2026-124889, CVE-2026-124890, CVE-2026-124891, CVE-2026-124892, CVE-2026-124893, CVE-2026-124894, CVE-2026-124895, CVE-2026-124896, CVE-2026-124897, CVE-2026-124898, CVE-2026-124899, CVE-2026-124901, CVE-2026-124902, CVE-2026-124903, CVE-2026-124905, CVE-2026-124906, CVE-2026-124907, CVE-2026-124909, CVE-2026-124910, CVE-2026-124912, CVE-2026-124913, CVE-2026-124914, CVE-2026-124915, CVE-2026-124917, CVE-2026-124918, CVE-2026-124919, CVE-2026-124922, CVE-2026-124924, CVE-2026-124926, CVE-2026-124927, CVE-2026-124929, CVE-2026-124930, CVE-2026-124931, CVE-2026-124932, CVE-2026-124933, CVE-2026-124934, CVE-2026-124935, CVE-2026-124938, CVE-2026-124939, CVE-2026-124940, CVE-2026-124941, CVE-2026-124942, CVE-2026-124948, CVE-2026-124951, CVE-2026-126132, CVE-2026-126133, CVE-2026-126134, CVE-2026-126135, CVE-2026-126136
Authoritative release dateNovember 12, 2026 at 12:13:26 UTC, from the dated Debian security announcement.
Authority revision dateNo separate revision date is provided by the authority.
Affected versionsDebian trixie thunderbird packages requiring this security update; the tracker explicitly identifies 1:140.12.0esr-1~deb13u1 as vulnerable.
Fixed versionthunderbird 1:153.7.0esr-1~deb13u1 for Debian trixie
CVSS base scoreNot provided by the authority
CVSS severityNot provided by the authority
Exploitation statusThe Debian advisory does not state exploitation in the wild.; no exploitation claim is inferred.

What Changed

Debian issues DSA-6621-1 for thunderbird flaws that can permit arbitrary code execution or information disclosure. The advisory and package tracker agree on the trixie security update.

What To Validate Now

  1. Inventory. Identify Debian suite, thunderbird package version and origin, responsible owners, deployment policy and relevant service or user exposure.
  2. Establish applicability. Match Debian 13 trixie and package origin to the advisory. Assess other suites or upstream installations against their own supported security guidance.
  3. Remediate. Apply thunderbird 1:153.7.0esr-1~deb13u1 through the Debian security repository using the approved maintenance process.
  4. Validate. Confirm the full installed package version including its epoch, and the running application version after relaunch. Retain rollout records and results for representative mail and calendar workflows.
  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

The update changes the packaged ESR line. Back up profiles and validate add-on and policy compatibility; use supported deployment and recovery procedures.

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.