Critical Apache HTTP/2 flaw allows unauthenticated remote code execution
Servers running Apache 2.4.55 to 2.4.70 with HTTP/2 enabled should upgrade to 2.4.71, and the archived mod_h2 project has no fixed release.
Servers running Apache 2.4.55 to 2.4.70 with HTTP/2 enabled should upgrade to 2.4.71, and the archived mod_h2 project has no fixed release.
Affected customers should rotate exposed secrets, since filing a charge dispute alone does not revoke a compromised key.
The introductory price doubles after November 30, so teams weighing a move should budget for the higher rate.
Organizations that left unused Qubole cross-account roles in place were exposed, and the researchers have not yet said how the attacker obtained the credentials.
Customers relying on Brev-hosted VMs need to confirm their instances were updated, since NVIDIA has not yet explained how the intruders got in.
Many sites were running end-of-life PHP versions, so the one-point-release fix could not be applied quickly everywhere.
Organisations running private repositories or GitHub Enterprise Server are not covered by GitHub's workflow hold, so they must check their own exposure.
The bugs remain unexploited so far, but AI is shortening the time between disclosure and attack for under-resourced teams.
Organisations are still checking exposure, and experts warn the fallout may take months to fully emerge.
Operators running PHP 8.1 or older have no official fix and must move to a supported branch.
Sites running PHP may need to take systems offline until fixes are applied, as attackers were already probing the weaknesses before the public warning.
Operators running PHP 8.1 or older face the most pressing risk, since no official fix is coming for those versions.
Operators running PHP on public sites face urgent patching, and no temporary workaround fully blocks the attacks.
Google is limiting early access to a model built for high-risk work before opening it more widely later.