F5 issued updates for ten security flaws in open-source NGINX. Two involve critical HTTP/2 vulnerabilities that can allow an unauthenticated remote attacker to execute code with the privileges of the NGINX worker process. CVE-2026-123007 concerns HTTP/2 flow-control handling; CVE-2026-123633 is a use-after-free flaw that applies when HTTP/2 requests are forwarded to an upstream server. F5 said it had not observed attacks in the wild at the time of its notice.
The affected version ranges differ by flaw. The fixed open-source releases include 1.31.9 for the mainline branch and 1.30.7 for the stable branch. Administrators need to compare their installed version, enabled protocol features, and packaging source with the applicable product advisory; a distribution or hosting provider may publish its own build number.
The disclosure includes vulnerabilities beyond the two HTTP/2 issues, so the full advisory matters even where HTTP/2 is not enabled. A lack of reported exploitation described the situation at the time of the notice and should not be read as a permanent status. Patch availability and exact exposure depend on the configuration in use.
Why it matters
An internet-facing HTTP/2 listener can create meaningful exposure, but the affected conditions and version ranges differ between flaws. The release numbers are a starting point, not a substitute for checking a distribution package or managed service. The statement that no exploitation had been observed was time-bound; current monitoring and the applicable vendor notice are needed to assess the risk after disclosure.
Sources and further reading
This story is written in its own words. These links identify the reporting and announcements used to verify the details above.




