The entry for the new CVE-2026-24072 from two days ago mentions openSUSE Leap 15.3, 15.4 and 15.5 as no longer supported but omits Leap 15.6, 16.0, 16.1 and Tumbleweed altogether.
I have a somewhat uncomfortable feeling with a distribution no longer offering CVE tracking in those challenging times like now or did I overlook something obvious.
A possible explanation is, the time stamps – the SUSE statement published via Planet openSUSE, is dated the 3rd of May 2026 – the CVE page was last modified on the 7th of May 2026 …
Possibly the CVE page will receive some more changes …
*) SECURITY: CVE-2026-24072: Apache HTTP Server: mod_rewrite elevation of privileges via ap_expr [boo#1263935]
An escalation of privilege bug in various modules in Apache HTTP 2.4.66 and earlier allows local .htaccess authors to read files with the privileges of the httpd user.
Users are recommended to upgrade to version 2.4.67, which fixes this issue.
Thanks for the information which was quite helpful. What still remains uncertain to me is why the official SUSE CVE still no longer mentions the latest openSUSE editions.
In the past it was very helpful to have a single place (SUSE CVE Website) where status of all vulnerabilites could have been tracked from a single place.
AFAICS, the Apache2 change related to CVE-2026-24072 are in a “waiting for release” state – about 23 hours ago the “factory-maintainer” submitted the changes for a final review before release – <https://build.opensuse.org/requests/1353166>
At a guess, the CVE status will be change once the repair hits the streets …
I’m not quite sure about that. If you take a look at the CVE page in question you could see, that openSuse 15.6 and up and also Tumbleweed are not even mentioned with status “affected”.
In the past you were able to track lifecycle of an CVE also for openSUSE on the SUSE CVE page, starting with “affected” and then transitioning to “released” over time with links to the related packages.