yousukezan[verified]@yousukezanGeneral
The post links to a Qiita article that explains CVE‑2026‑49975, but it provides no evidence of a PoC, exploit code, active exploitation, patch, or technical details.
Cyber Security News[verified]@The_Cyber_NewsExploit
A publicly available PoC exploit script in Python has been released on GitHub for CVE‑2026‑49975, a critical DoS vulnerability in Apache HTTP Server that allows remote memory exhaustion without authentication; operators should upgrade to v2.4.68 or later to mitigate.
エックスサーバー【公式】[verified]@xserverjpPatch
XServer announced that CVE‑2026‑49975, a vulnerability affecting HTTP/2, is under disclosure. They have temporarily disabled HTTP/2 as a workaround while preparing a permanent patch.
bearstech[verified]@bearstechDisclosure
The text provides basic disclosure details for CVE‑2026‑49975, describing its effect on Apache HTTP Server 2.4.17‑2.4.67 via excessive memory allocation without mentioning PoC, exploits, or patches.
Yasuhiro Morishita[verified]@OrangeMorishitaGeneral
The memo explains the CVE-2026-49975 "HTTP/2 Bomb" but does not provide a PoC, exploit, active exploitation evidence, patch, or debunking claim.
bearstech[verified]@bearstechPatch
The tweet links to an HAProxy article explaining how the product’s architecture limits the risk of a HTTP/2 bomb, noting per-connection memory constraints as a mitigation.
スタードメイン【公式】[verified]@stardomainjpDisclosure
An advisory was issued for CVE-2026-49975 affecting HTTP/2, noting the vulnerability could cause service interruption. A temporary workaround—disabling HTTP/2 and switching to HTTP/1.1—was implemented without evidence of active exploitation or detailed technical data.
GovCERT.CZ[verified]@GOVCERT_CZPatch
The post details CVE‑2026‑49975 as a DoS flaw in HTTP/2 implementations, provides specific patch versions for NGINX and Apache, and recommends disabling HTTP/2 on unpatched systems.