CVE-2026-42535 is a moderate-severity path handling vulnerability in the mod_dav_fs component of Apache HTTP Server affecting version 2.4.67 and earlier. The flaw allows a WebDAV content author to directly manipulate trusted DAV property databases due to improper path handling in WebDAV filesystem operations. By abusing this condition, an attacker with the ability to author WebDAV content can interfere with internal DAV property storage that is expected to remain trusted by the server. The documented consequence is instability in Apache child processes, including process crashes.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability affecting IBM HTTP Server configurations with mod_dav loaded.
A path handling vulnerability in Apache HTTP Server mod_dav_fs allowing WebDAV authors to manipulate trusted DAV property databases.
A vulnerability addressed in the Apache HTTP Server 2.4.68 security update.
Apache HTTP Server mod_dav_fs vulnerability related to WebDAV functionality, fixed in version 2.4.68.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.