Date: Mon, 11 May 2026 19:53:11 -0500 From: Tim Daneliuk <thronobulax@gmail.com> To: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Python 3.11 Open CVE Resolution? Message-ID: <c0d7cfb2-7456-442f-b587-698d40f61998@gmail.com> In-Reply-To: <d27e02e3-5f26-4f12-9283-930f72127732@gmail.com> References: <922c5133-a4bc-4752-aaad-6b569a354745@gmail.com> <CAHu1Y71RzDqH9NGEaEtN0uNssM_aRQEZ9=v35cfYCEB6ituGwA@mail.gmail.com> <6501d762-db9b-4979-a53f-b57ef848f1ec@gmail.com> <d27e02e3-5f26-4f12-9283-930f72127732@gmail.com>
index | next in thread | previous in thread | raw e-mail
On 5/4/26 18:38, Tim Daneliuk wrote: > On 5/4/26 16:34, Tim Daneliuk wrote: >> On 5/4/26 12:17, Michael Sierchio wrote: >>> On Mon, May 4, 2026 at 1:02 PM Tim Daneliuk <thronobulax@gmail.com> wrote: >>>> >>>> A lot of port upgrades are failing because of open CVEs on Python 3.11 on 13.5-STABLE. >>>> >>>> Do we have a likely ETA for resolution? I prefer not to disable vulnerability checking. >>> >>> By resolution do you mean availability of a point release for Python, >>> such as 3.11.15? >>> >> >> Yes. This has not appeared in ports yet so far as I know. > > I should correct this. 3.11.15 is in the ports, but the current .2 subversion is still > shown vulnerabilities. > > This is preventing all manner of other ports updates. Nevermind. I managed to somehow miss that 13-stable was EOL. A move to 14-stable on a few servers made everything happy again (but the CVEs are still not resolved). D'Oh ...home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c0d7cfb2-7456-442f-b587-698d40f61998>