Apache HTTP Server is widely used; Apache Lounge Windows builds are common. Writable default install directory enables service tampering and code execution across many Windows servers.
CVE-2026-89282
Apache Lounge Windows installer leaves C:\ install dir writable by Authenticated Users.
Is CVE-2026-89282 being exploited?
Not confirmed. CVE-2026-89282 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.48% probability of exploitation in the next 30 days.
How severe is CVE-2026-89282?
CVE-2026-89282 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-89282?
Not known from our data. No patch reference has been recorded for CVE-2026-89282, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-89282 affect?
CVE-2026-89282 affects Apache Lounge Windows distribution of Apache HTTP Server, Windows hosts with default Apache install to C:\ (Authenticated Users write). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-89282?
Remove Authenticated Users write, tighten C:\Apache* ACLs, move install off C:\ and apply vendor updates when available.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated local users can modify server files/binaries, enabling persistence, service hijack or remote code execution as the web service account.
Immediate action required
- affected< Apache 2.4.68-260920 Win64
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- none
- automatable
- yes
- technical impact
- total
Assessed by CISA 23 Sept 2026 (SSVC 2.0.3).
timeline
- 22 Sept 2026Published
- 23 Sept 2026CISA SSVC assessment: exploitation none · 1 day later
- 23 Sept 2026CVE record last updated · same day later
- 24 Sept 2026Analysed by vulneraibility.com · 1 day later
- 17 Oct 2026First proof-of-concept repository on GitHub (unvetted) · 23 days later
- Linkhttpd.apache.org /download.cgi
- Linkatos.net /en/lp/cybershield/a-tale-of-several-hijacks-and-what-it-taught-me-about-runtime
- Linkapachelounge.com /viewtopic.php?t=9515
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.