CVE-2026-42535

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-08. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.1Exploit: NoneExposed: 0

A fix is available — apply it.

A path handling issue in mod_dav_fs in Apache 2.4.67 and earlier allows a WebDAV content author to directly manipulate trusted DAV property databases, potentially causing child process crashes.

Users are recommended to upgrade to version 2.4.68, which fixes this issue.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
42.0%
KEV
Not listed

Published

June 8, 2026

Last Modified

June 9, 2026

Advisory Details (2)

Auto-updated Jun 9, 2026
⚠️ Active exploitation confirmed. Patch available.
generic

oss-security - CVE-2026-42535: Apache HTTP Server: mod_dav_fs protected directory access

http://www.openwall.com/lists/oss-security/2026/06/08/8
generic Patch Available🔴 Active Exploitation

Apache HTTP Server 2.4 vulnerabilities - The Apache HTTP Server Project

https://httpd.apache.org/security/vulnerabilities_24.html

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuapache2-utils (2.4.66-2ubuntu2.4) @ resolute2026-07-16ubuntu
redhathttpd-0:2.4.63-13.el10_2.42026-07-01redhat
redhathttpd-main-2.4.68-1.hum12026-06-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 136× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 221 total refreshes for this CVE.

  1. 2026-07-23 03:11 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-16 09:47 UTCVendor advisory
  10. 2026-07-16 09:47 UTCGHSA enrichment
  11. 2026-07-16 02:20 UTCVendor advisory
  12. 2026-07-16 02:20 UTCGHSA enrichment
  13. 2026-07-15 22:27 UTCVendor advisory
  14. 2026-07-15 22:27 UTCGHSA enrichment
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 02:00 UTCEPSS rescore
  17. 2026-07-14 21:23 UTCVendor advisory
  18. 2026-07-14 21:23 UTCGHSA enrichment
  19. 2026-07-14 16:43 UTCVendor advisory
  20. 2026-07-14 16:43 UTCGHSA enrichment
  21. 2026-07-14 12:51 UTCVendor advisory
  22. 2026-07-14 12:51 UTCGHSA enrichment
  23. 2026-07-14 02:49 UTCVendor advisory
  24. 2026-07-14 02:49 UTCGHSA enrichment
  25. 2026-07-13 22:30 UTCEPSS rescore
Show 75 more
  1. 2026-07-13 06:13 UTCEPSS rescore
  2. 2026-07-12 10:16 UTCVendor advisory
  3. 2026-07-12 10:16 UTCGHSA enrichment
  4. 2026-07-12 05:46 UTCEPSS rescore
  5. 2026-07-12 05:18 UTCVendor advisory
  6. 2026-07-12 05:18 UTCGHSA enrichment
  7. 2026-07-12 00:17 UTCVendor advisory
  8. 2026-07-12 00:17 UTCGHSA enrichment
  9. 2026-07-11 20:25 UTCVendor advisory
  10. 2026-07-11 20:25 UTCGHSA enrichment
  11. 2026-07-11 16:33 UTCVendor advisory
  12. 2026-07-11 16:33 UTCGHSA enrichment
  13. 2026-07-11 12:41 UTCVendor advisory
  14. 2026-07-11 12:41 UTCGHSA enrichment
  15. 2026-07-11 08:49 UTCVendor advisory
  16. 2026-07-11 08:48 UTCGHSA enrichment
  17. 2026-07-11 08:27 UTCEPSS rescore
  18. 2026-07-11 04:49 UTCVendor advisory
  19. 2026-07-11 04:49 UTCGHSA enrichment
  20. 2026-07-10 21:30 UTCVendor advisory
  21. 2026-07-10 21:30 UTCGHSA enrichment
  22. 2026-07-09 19:10 UTCEPSS rescore
  23. 2026-07-09 09:43 UTCVendor advisory
  24. 2026-07-09 09:43 UTCGHSA enrichment
  25. 2026-07-09 04:44 UTCVendor advisory
  26. 2026-07-09 04:44 UTCGHSA enrichment
  27. 2026-07-08 21:26 UTCVendor advisory
  28. 2026-07-08 21:25 UTCGHSA enrichment
  29. 2026-07-08 15:57 UTCVendor advisory
  30. 2026-07-08 15:57 UTCGHSA enrichment
  31. 2026-07-08 15:15 UTCEPSS rescore
  32. 2026-07-08 07:36 UTCGHSA enrichment
  33. 2026-07-08 03:32 UTCGHSA enrichment
  34. 2026-07-07 13:46 UTCEPSS rescore
  35. 2026-07-06 16:27 UTCEPSS rescore
  36. 2026-07-06 16:27 UTCEPSS rescore
  37. 2026-07-06 02:23 UTCEPSS rescore
  38. 2026-07-06 02:23 UTCEPSS rescore
  39. 2026-07-06 01:46 UTCGHSA enrichment
  40. 2026-07-05 21:54 UTCGHSA enrichment
  41. 2026-07-05 17:40 UTCGHSA enrichment
  42. 2026-07-05 02:30 UTCEPSS rescore
  43. 2026-07-04 20:16 UTCGHSA enrichment
  44. 2026-07-04 15:06 UTCGHSA enrichment
  45. 2026-07-04 06:31 UTCEPSS rescore
  46. 2026-07-04 00:06 UTCGHSA enrichment
  47. 2026-07-03 20:13 UTCGHSA enrichment
  48. 2026-07-03 16:20 UTCGHSA enrichment
  49. 2026-07-03 09:26 UTCGHSA enrichment
  50. 2026-07-03 03:19 UTCGHSA enrichment
  51. 2026-07-02 23:23 UTCGHSA enrichment
  52. 2026-07-02 19:30 UTCGHSA enrichment
  53. 2026-07-02 15:37 UTCGHSA enrichment
  54. 2026-07-02 11:24 UTCGHSA enrichment
  55. 2026-07-02 06:41 UTCGHSA enrichment
  56. 2026-07-02 02:49 UTCGHSA enrichment
  57. 2026-07-01 22:57 UTCGHSA enrichment
  58. 2026-07-01 18:42 UTCGHSA enrichment
  59. 2026-07-01 15:06 UTCEPSS rescore
  60. 2026-07-01 14:49 UTCGHSA enrichment
  61. 2026-07-01 10:47 UTCGHSA enrichment
  62. 2026-07-01 06:55 UTCGHSA enrichment
  63. 2026-07-01 00:46 UTCGHSA enrichment
  64. 2026-06-30 23:22 UTCEPSS rescore
  65. 2026-06-30 20:53 UTCGHSA enrichment
  66. 2026-06-30 16:30 UTCGHSA enrichment
  67. 2026-06-30 07:46 UTCGHSA enrichment
  68. 2026-06-30 03:51 UTCGHSA enrichment
  69. 2026-06-29 23:58 UTCGHSA enrichment
  70. 2026-06-29 19:52 UTCGHSA enrichment
  71. 2026-06-29 15:59 UTCGHSA enrichment
  72. 2026-06-29 14:06 UTCEPSS rescore
  73. 2026-06-29 12:07 UTCGHSA enrichment
  74. 2026-06-29 08:14 UTCGHSA enrichment
  75. 2026-06-28 23:56 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-42535?
CVE-2026-42535 is a critical vulnerability published on June 8, 2026. A path handling issue in moddavfs in Apache 2.4.67 and earlier allows a WebDAV content author to directly manipulate trusted DAV property databases, potentially causing child process crashes. Users are recommended to upgrade to version 2.4.68, which fixes this issue.
When was CVE-2026-42535 disclosed?
CVE-2026-42535 was first published in the National Vulnerability Database on June 8, 2026, with the most recent update on June 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42535 actively exploited?
CVE-2026-42535 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 42.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-42535?
CVE-2026-42535 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-42535?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42535, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-42535

Explore →

Is Your Infrastructure Affected by CVE-2026-42535?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.