8.2.11 release announcement calls itself a security release. Somewhat strangely, the contemporaneous 8.1 release doesn't call itself a security release. I don't see anything in particular which jumps out as significantly security-impactful, other than maybe: - Fixed bug GH-12073 (Segfault when freeing incompletely initialized closures). - Fixed bug GH-12060 (Internal iterator rewind handler is called twice). - Fix memory leak when setting an invalid DOMDocument encoding. - Fixed memory leak with failed SQLPrepare.
Did it ever become clear what the security issues (if any) were? Otherwise I would propose to close this bug.
Maybe the segfault? But pretty much every release of PHP is a security release & we've stabilized several since this bug was opened. RESOLVED->OBSOLETE is the easy way out.
This is fine with me. @ajak: if you feel differently please re-open the bug.