[omniORB] omniORB and omniORBpy 4.3.5 released with security fixes
Duncan Grisby
duncan at grisby.org
Thu Nov 12 16:04:43 UTC 2026
(Replying to two messages at once)
On Thu, 2026-11-12 at 16:18 +0100, Thomas Braun via omniORB-list wrote:
> thanks for the release and the info. Are you doing CVEs? I want to
> ping downstream packagers and that would help getting it quickly
> integrated.
I was not intending to do so, but it could probably be done. I'm not
sure who would allocate a CVE number for omniORB, though.
>
> Is the bugfix in revision r6833 only?
Yes.
One issue had actually already been fixed in the 4_4 development / beta
branch; the other one was fixed in revision r6835.
> And is the bug present in earlier versions as well? From my playing
> around the patch applies onto 4.2.5 as well.
Yes, it is in older versions, and the same fix will work on 4.2.x, but
considering that 4.3.0 was released in January 2022, I would really
consider 4.2.x out of support.
Duncan.
--
Duncan Grisby <duncan at grisby.org>
More information about the omniORB-list
mailing list