The PHP language, runtime, frameworks and production ecosystem.
Showing 1–12 of 12 dossiers
The October release is more than a version bump: PHP server operators should patch document-root and header risks, then test worker/thread budgets and stricter proxy defaults before upgrading.
PHP's official extension installer can now install multiple packages in one command and select missing project extensions without prompting. PIE 1.5 also improves attestation verification for its own updates.
The bug is a useful warning for AI application plumbing: turning a user-supplied URL into a model attachment also turns the application server into a network client unless the adapter enforces an outbound trust boundary.
The sharpest operational trap is CVE-2026-91768: PHP-FPM’s listen.allowed_clients can treat an allowed IPv6 address as an entire /96 prefix. Teams relying on that ACL should patch rather than assuming the configured address restriction is exact.
Vet turns dependency updates from an implicit trust decision into an explicit, reviewable one for Laravel, Symfony, WordPress and plain PHP projects, with optional local coding-agent review layered underneath the human trust decision.
This is a patch-and-hunt event rather than a routine Commerce security release. Exploitation began before the vendor fix existed, and Adobe plus independent responders recommend remediation that goes beyond installing the hotfix when compromise is suspected.
The change moves maintenance work earlier in the contribution funnel: instead of filing a report and waiting for a maintainer to reproduce it, package users are being asked to arrive with an executable patch candidate. It is a real workflow experiment, but Otwell's prediction that this becomes the norm should remain a founder/maintainer view rather than an industry fact.
HIPAA support moves Laravel Cloud into a class of regulated workloads that shared application hosting could not safely claim. Private Cloud supplies dedicated tenancy, encryption, SSO/SAML, backups and a BAA path, while application-level access control, audit logging and PHI handling remain the developer’s responsibility.
Laravel now has a framework-native approval flow for AI tools: approvable tools can pause an agent, surface arguments and reasons, then resume the same persisted conversation after a human decision.
Reprise was already Symfony’s recommended modern bundler integration, but 1.0 changes the adoption decision: applications can now depend on a documented compatibility contract rather than an experimental 0.x API, while Encore remains available in low-maintenance mode.
Symfony’s official LSP has moved quickly beyond its August 17 launch. Ten releases in six days added Docker-hosted PHP indexing, Zed and OpenCode support, richer Twig and Doctrine navigation, XML service support and real-application performance tests; the project is still explicitly beta.
Adobe Commerce and Magento merchants should treat CVE-2026-71362 as an urgent patch: independent security telemetry reports exploitation attempts even though Adobe’s bulletin still says it has not observed exploitation in the wild.
PHP continues to run a large share of the web while its runtime, type system, frameworks and tooling keep improving. The changes that matter are not limited to headline language releases; package security, deployment practice, performance work and framework decisions can have a larger effect on an existing application.
This page collects practical PHP developments for people who ship and maintain software. BTN reads the RFCs, release notes and project documentation, then looks at compatibility, upgrade effort and operational consequences. The aim is to make a new feature or ecosystem change useful in context, especially for teams balancing modernisation with the reality of long-lived production code.
Coverage also follows the health of the package and hosting ecosystem. Composer changes, supported-version policies and widely used dependencies can determine the safest upgrade path for far more applications than a new syntax feature. Practical examples matter more here than arguments about whether PHP is fashionable.