upvote
The PHP 8.6.0 stable release will include the fixes for all applicable vulnerabilities.
reply
And add a few more unknown CVE, as perpetual Beta and DevOps culture does by design.

The old approach of out-pacing adversaries though mutation rates is over, given an entire FOSS code-audit looking/fuzzing for 0-days can now be done in under a day. In retrospect, over 700 reported LPE and 280 kernel CVE were dropped in the past 3 months from "LLM". This is not going to stop anytime soon.

To be honest, its very nostalgic as kids would clown each others servers in the early days. Ultimately leading to a more robust OS for everyone. =3

reply
[dead]
reply
There are two separate teams handling both, the Release Managers and website team do PHP 8.6 and the Security team works on the vulnerability. :)
reply
”These releases are part of PHP’s regular four-week release cycle and will address security“

So I’m not sure what you mean by “before you get excited”? This is their normal release cycle, not some new emergency patch release. Although based on recent events, I see how this could be confused.

reply
The notes say "The highest severity is CRITICAL.... Users are strongly encouraged to prepare to upgrade promptly once the releases become available. Technical details and fixed version numbers will be published alongside the releases."

I'd say this sounds pretty serious.

reply
No doubt, I’m sure they are indeed “critical”, my point is that this is part of the regular cadence of maintenance releases. Every PHP server SHOULD upgrade. But that’s no different than any other language, when a security/ maintenance release comes out, you upgrade.

The parent comment seemed to be mistaking this for another unplanned security release like we had recently for the 2 RCE vulnerabilities.

reply
There are critical vulns patched in the older releases at the same time.
reply
we run serverpilot, it auto patches our php server.
reply
Link to this?
reply
reply
”These releases are part of PHP’s regular four-week release cycle and will address security”
reply
another one?
reply