CVE-2026-29169

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-04. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A NULL pointer dereference in mod_dav_lock in Apache HTTP Server 2.4.66 and earlier may allow an attacker to crash the server with a malicious request.mod_dav_lock is not used internally by mod_dav or mod_dav_fs.

The only known use-case for mod_dav_lock was mod_dav_svn from Apache Subversion earlier than version 1.2.0.

Users are recommended to upgrade to version 2.4.66, which fixes this issue, or remove mod_dav_lock.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
EPSS PROB
1.6%
EPSS %ILE
74th
KEV
Not listed

Published

May 4, 2026

Last Modified

May 5, 2026

Advisory Details (2)

Auto-updated May 4, 2026
⚠️ Active exploitation confirmed. Patch available.
generic

oss-security - CVE-2026-29169: Apache HTTP Server: mod_dav_lock indirect lock crash

http://www.openwall.com/lists/oss-security/2026/05/04/20
genericMentions a patch (unverified)🔴 Active Exploitation

Apache HTTP Server 2.4 vulnerabilities - The Apache HTTP Server Project

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

Vendor Advisories for CVE-2026-29169(12)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(10)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuapache2-utils (2.4.66-2ubuntu2.1) @ resolute2026-08-23ubuntu
ubuntuapache2-utils (2.4.18-2ubuntu3.17+esm18) @ xenial2026-08-23ubuntu
redhatinsights-proxy/insights-proxy-container-rhel9:17864336562026-08-11redhat
redhathttpd-0:2.4.63-1.el10_0.42026-07-28redhat
redhathttpd:2.4-8100020260714175253.489197e62026-07-21redhat
redhathttpd-0:2.4.62-13.el9_8.52026-07-20redhat
redhathttpd-0:2.4.63-13.el10_2.42026-07-01redhat
redhatmod_dav_lock.so2026-06-22redhat
redhatjbcs-httpd24-httpd-0:2.4.62-13.el7jbcs2026-06-22redhat
redhathttpd-main-2.4.67-1.hum12026-05-13redhat

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.

Affected Packages

(9 across 9 ecosystems)
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.67-r0: fixed in 2.4.67-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.67-r0: fixed in 2.4.67-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.67-r0: fixed in 2.4.67-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.67-r0: fixed in 2.4.67-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.67-r0: fixed in 2.4.67-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
apache22.4.48-3.1 ... 2.4.66-8 (82 versions)
  • every version up to 2.4.67-1~deb11u1: fixed in 2.4.67-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
apache22.4.57-2 ... 2.4.67-1~deb12u1 (46 versions)
  • every version up to 2.4.67-1~deb12u2: fixed in 2.4.67-1~deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
apache22.4.65-2 ... 2.4.67-1~deb13u1 (22 versions)
  • every version up to 2.4.67-1~deb13u2: fixed in 2.4.67-1~deb13u2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
apache22.4.65-2 ... 2.4.67-1~deb13u3 (24 versions)
  • every version up to 2.4.67-1: fixed in 2.4.67-1
—

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 7× in last 7d / 23× 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 286 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-29169?
CVE-2026-29169 is a high vulnerability published on May 4, 2026. A NULL pointer dereference in moddavlock in Apache HTTP Server 2.4.66 and earlier may allow an attacker to crash the server with a malicious request.moddavlock is not used internally by moddav or moddav_fs. The only known use-case for moddavlock was moddavsvn from Apache Subversion earlier than…
When was CVE-2026-29169 disclosed?
CVE-2026-29169 was first published on May 4, 2026, with the most recent update on May 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-29169 actively exploited?
CVE-2026-29169 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.6% probability of exploitation in the next 30 days (74th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-29169?
CVE-2026-29169 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-29169?
A fix for CVE-2026-29169 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-29169 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-29169

Explore →

Is Your Infrastructure Affected by CVE-2026-29169?

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

Book a Demo →Browse All CVEs