# PHP 5.4.16 and PHP 5.3.26 released!

- Thread: https://externals.io/message/67639
- Original archive: https://news-web.php.net/php.internals/67639
- Started by Pierre Schmitz on 2013-06-07T04:34:35+00:00
- Messages: 2
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #67639 — Pierre Schmitz — 2013-06-07T04:34:35+00:00

URL: https://externals.io/message/67639#67639

Am 07.06.2013 01:58, schrieb Stas Malyshev:
> Hello!
> 
> The PHP development team announces the immediate availability of PHP
> 5.4.16 and PHP 5.3.26. These releases fix about 15 bugs, including
> CVE-2013-2110. All users of PHP are encouraged to upgrade to PHP 5.4.16.
> PHP 5.3.26 is recommended for those wishing to remain on the 5.3 series.

Is there a way to access the content of the relevant bug report here?
https://bugs.php.net/bug.php?id=64879 Who is allowed to see these
private reports?

Greetings,

Pierre

-- 
Pierre Schmitz, https://pierre-schmitz.com

---

## #67642 — Ferenc Kovacs — 2013-06-07T12:05:31+00:00

URL: https://externals.io/message/67639#67642 · In reply to: #67639

> Am 07.06.2013 01:58, schrieb Stas Malyshev:
> > […]
>
> Is there a way to access the content of the relevant bug report here?
> https://bugs.php.net/bug.php?id=64879 Who is allowed to see these
> private reports?
>
>
private bugs can be only accessed by the php security team and some
security people from vendors:
http://git.php.net/?p=web/bugs.git;a=blob;f=include/trusted-devs.php
I think that private bugs like that should be made public after the fixed
version release, just like others do the same:
https://bugzilla.redhat.com/show_bug.cgi?id=964969
usually searching for a CVE number on google works (after the fix is
released).

-- 
Ferenc Kovács
@Tyr43l - http://tyrael.hu