Debian Updates PHP 8.4 for Multiple Security Vulnerabilities
Quick Answer
Update Debian trixie php8.4 to 8.4.28-1~deb13u1, 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 php8.4 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. Validate active PHP workers, application requests, extensions and scheduled CLI jobs after updating. Retain before-and-after versions, package transactions and test outcomes.
Last verified: 2026-11-19 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | php8.4 on Debian 13 (trixie) |
|---|---|
| Advisory | DSA-6641-1 |
| CVEs | CVE-2026-115560, CVE-2026-126714, CVE-2026-127960, CVE-2026-128064, CVE-2026-128090, CVE-2026-129289, CVE-2026-129291, CVE-2026-129292, CVE-2026-129496, CVE-2026-129506, CVE-2026-129538, CVE-2026-15353 |
| Authoritative release date | 2026-11-19T14:29:13Z — dated Debian security-announce message. |
| Authority revision date | No separate material revision is stated for this release. |
| Affected versions | Debian 13 (trixie) php8.4 packages before the corrected 8.4.28-1~deb13u1 build identified by DSA-6641-1. |
| Fixed version | php8.4 8.4.28-1~deb13u1 |
| CVSS base score | Not provided by the authority |
| CVSS severity | Not provided by the authority |
| Exploitation status | The cited authority does not confirm exploitation of these vulnerabilities in the wild.; no exploitation claim is inferred. |
What Changed
The PHP update addresses code execution, denial of service, information disclosure, privilege escalation and cross-site scripting.
What To Validate Now
- Inventory. Identify Debian trixie systems, installed php8.4 packages, application use, dependent services and responsible owners.
- 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.
- Remediate. Apply the supported Debian security package update, refresh affected deployment images and restart dependent long-running processes where required.
- Validate. Validate active PHP workers, application requests, extensions and scheduled CLI jobs after updating. Retain before-and-after versions, package transactions and test outcomes.
- 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
Exposure varies with the affected PHP feature and application input path. Restart long-running workers through the approved service procedure.
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.

