PHP vulnerabilities
Summary
Aleksey Solovev and Nikita Sveshnikov discovered that PHP improperly handled NUL bytes when preparing SQL queries in the PDO Firebird driver. An attacker could possibly use this issue to perform SQL injection attacks. (CVE-2025-14179) It was discovered that PHP incorrectly handled certain encoding names in mbstring. An attacker could possibly use this issue to obtain sensitive information or cause a denial of service. This issue only affected Ubuntu 25.10 and Ubuntu 26.04 LTS. (CVE-2026-6104) It was discovered that PHP incorrectly handled object references while parsing crafted SOAP requests. A remote attacker could possibly use this issue to execute arbitrary code. (CVE-2026-6722) It was discovered that PHP incorrectly sanitized certain data in the PHP-FPM status page. A remote attacker could possibly use this issue to inject arbitrary JavaScript code. (CVE-2026-6735) It was discovered that PHP had an encoding mismatch in mbstring. An attacker could possibly use this issue to cause PHP to crash, resulting in a denial of service. (CVE-2026-7259) It was discovered that PHP incorrectly handled SOAP session persistence after errors. A remote attacker could possibly use this issue to obtain sensitive information or cause PHP to crash, resulting in a denial of service. (CVE-2026-7261) It was discovered that PHP incorrectly handled missing values in SOAP typemap decoding. A remote at Affected Ubuntu releases: 26.04, 25.10, 24.04, 22.04. CVEs: CVE-2026-7259, CVE-2026-6722, CVE-2025-14179, CVE-2026-7261, CVE-2026-7568, CVE-2026-7263, CVE-2026-7262, CVE-2026-6104….
- Ubuntu 26.04
- Ubuntu 25.10
- Ubuntu 24.04
- Ubuntu 22.04
Official advisory · medium-confidence parse· fetched 3 hours ago·verify at source
Mitigation checklist
- Apply available updates: `sudo apt update && sudo apt upgrade` (a standard system update installs the fix).
Official advisory · medium-confidence parse· fetched 3 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.