CVE Tools

CVE-2026-42356

Apache HTTP Server: limited RCE for some internal redirects to non-CGI files in CGI directories

No known exploitation. EPSS puts it in the 39th percentile. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

  • Apache Software Foundation Apache HTTP ServerAffected: ≥ 2.4.60, ≤ 2.4.68Upgrade to: after 2.4.68Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check your Apache HTTP Server version and whether CGI is enabled on any directory.
  2. If you run Apache between version 2.4.60 and 2.4.68 with CGI enabled, treat this as affecting you.
  3. Upgrade Apache HTTP Server to version 2.4.69 or later.
  4. If you cannot upgrade immediately, disable CGI execution on directories you don't actively need it for.
  5. Confirm with your hosting provider or IT team that the server is patched.

What it is

From the CVE record

Deployment of wrong handler vulnerability in Apache HTTP Server allows the target of some internal redirects from CGI programs to also be treated as CGI and executed. The target must already be in a directory enabled for CGI and have no other extension understood by mod_mime. This issue affects Apache HTTP Server: from 2.4.60 through 2.4.68.

In plain language

Written by AI from the record

A flaw in Apache HTTP Server can let an attacker run code on your server under specific CGI misconfigurations, so if you run Apache with CGI enabled you should update to version 2.4.69 now.

Apache HTTP Server versions 2.4.60–2.4.68 mishandle internal redirects from CGI scripts, causing non-CGI target files in CGI-enabled directories (without a mod_mime-recognized extension) to be executed as CGI, enabling limited unauthenticated remote code execution.

If you're affected

  • Server takeover risk
  • Website defacement
  • Data exposure via code execution
  • Operational disruption

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS39th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.5% chance of exploitation activity in the next 30 days, which ranks it in the 39th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

8 events over 5 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Patch availablerecord updated
  3. Publishedweakness classified, record updated, record updated

Affected products

Technical detail

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

Scored 3.7 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity LowData modification is possible but limited in scope or consequence
  • Availability NoneNo availability impact

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Apache HTTP Server, not every advisory.