Urgent.News

What's breaking now, across thousands of outlets.

Tech

Critical RCE Vulnerability in Apache HTTP Server

Article URL: https://www.wiz.io/blog/cve-2026-119618-rce-apache-http-server-vulnerability Comments URL: https://news.ycombinator.com/item?id=50462177 Points: 308 # Comments: 146

A critical synchronization vulnerability (CVE-2026-119618) has been discovered in the HTTP/2 module (mod_http2) of the Apache HTTP Server. The issue arises from a race condition in the assign_headers() function of the module, which handles shared resources. A remote, unauthenticated attacker can exploit this flaw to corrupt heap memory, enabling arbitrary code execution (RCE).

As of now, no exploit has been reported in the wild. The vulnerability was independently identified by Anthropic and Google Cloud's Vulnerability Research Team. Wiz data indicates that 64% of cloud environments have resources susceptible to this vulnerability, with 51% having publicly exposed instances. This threat can serve as an entry point for lateral movement in cloud environments, potentially exposing adjacent microservices or cloud metadata endpoints.

To mitigate the risk, users are advised to upgrade their Apache HTTP Server to version 2.4.71 or later. If immediate patching is not feasible, disabling HTTP/2 support can eliminate the attack vector. This vulnerability affects deployments utilizing HTTP/2 capabilities on the Apache HTTP Server within specific version ranges.

Written by urgent.news from Hacker News's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Every outlet that reported this, and when →

Read the original at wiz.io →

More in Tech

Publish a Chrome Extension: 6 Steps and a Review Checklist

Originally published on ExtensionLaunch . To publish a Chrome extension, you need more than working code: the Chrome Web Store reviews your manifest, your permissions and your privacy answers before…

  • Developer registration involves $5 fee, dashboard verification, and brand setup if applicable
  • Narrow permissions, root manifest.json, and privacy tab thoroughness are critical for approval

I Wasted 3 Days on Google Drive 'Open With' OAuth — Here's Everything I Learned

Three days. That's how long it took me to fix a single OAuth error that, in hindsight, had a five-minute solution. The catch? The fix was in a place I never thought to look.

  • Three days spent resolving OAuth error with Google Drive Open With app
  • Redirect URI mismatch due to ngrok URL hard-coded in openUrlTemplate
  • Actual redirecturi obtained from Chrome DevTools and queried via access token

How to Plan Separate WAF Rate Limits for Different URL Paths

A login endpoint and a product catalog rarely need the same traffic policy. Login attempts can be expensive or security-sensitive, while browsing often produces legitimate bursts.

  • Distinguish URL paths by functionality (e.g., /login vs /api/search)
  • Determine rate limit measurements (IP, account, time window, threshold)
  • Verify SafeLine's support for path-specific rate limits through testing

Shared WAF Limits vs Path-Specific Limits: How to Choose Enforcement Placement

A login endpoint, a search page, and a static asset directory rarely have the same traffic pattern. Applying one request threshold across all three can create a difficult tradeoff: tolerate expensive…

  • Shared WAF limits offer operational simplicity but lack precision in traffic enforcement.
  • Path-specific limits allow application context and precise control over endpoint budgets.

More from Thursday 12 November →