/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Security firm Calif says it used OpenAI's Codex to discover HTTP/2 Bomb, a remote DoS exploit affecting web servers like Nginx, Apache HTTPD, and Microsoft IIS

Cybersecurity researchers have discovered a remote denial-of-service exploit that affects major web servers, including NGINX

The Hacker News

Context & Ripple Effects

The reported flaw lands in a recurring HTTP/2 security arc. Related coverage of Rapid Reset showed that protocol-level weaknesses can enable record-setting DDoS attacks and are difficult to eliminate because every affected web server must be patched.

Earlier Apache coverage similarly tied a web-server flaw to active exploitation and a large installed base. This case broadens the immediate concern across NGINX, Apache HTTPD, and Microsoft IIS while adding Codex-assisted discovery as the notable new element.

First-order effects

  • Operators using affected NGINX, Apache HTTPD, or Microsoft IIS deployments must assess exposure and apply vendor mitigations or patches once available, because the reported issue enables remote denial of service.
  • Calif’s claim gives OpenAI’s Codex a prominent role in finding a security-relevant web-infrastructure flaw, increasing scrutiny of how AI-assisted research is validated and disclosed.

Second-order effects

  • CDN, hosting, and enterprise security teams may tighten HTTP/2 monitoring and DDoS controls, since a remotely triggered server-side weakness can create disruption beyond an individual application.
  • The overlap with prior HTTP/2 incidents will pressure server vendors and operators to coordinate remediation; uneven patching leaves attackers able to target the lagging portion of the ecosystem.

Third-order effects

  • If AI-assisted vulnerability research becomes repeatable, the time between finding flaws in widely deployed infrastructure and requiring defensive action could shrink for both vendors and operators.
  • Repeated HTTP/2 incidents point to a structural security problem in shared web protocols: effective risk reduction depends on ecosystem-wide deployment of fixes, not solely on a patch from one supplier.

The trend: This is one data point in the convergence of AI-accelerated security research and persistent protocol-layer DDoS risk across the web’s common server stack.

Discussion

  • @xorninja @xorninja on x
    When the team walked me through this research, I found myself back in 2012. That year, @julianor and I discovered CRIME, a compression oracle that recovered cookies from compressed HTTP headers. I was at Google at the time, so I was asked to review the fix, which became part of
  • @mysk_co @mysk_co on x
    While nginx and Apache httpd are patched, Microsoft IIS isn't. Microsoft is again too slow to address a vulnerability. Will Microsoft take legal action against this disclosure?
  • @calif_io @calif_io on x
    Introducing HTTP/2 Bomb: a remote DoS in nginx, Apache httpd, Microsoft IIS, Envoy, and Cloudflare Pingora. A single client pins 32GB of server memory in 10s. Found by Codex. Blog post: https://blog.calif.io/... PoCs: https://github.com/...