How severe is CVE-2026-42535?

No CVSS score has been assigned to CVE-2026-42535 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-42535?

CVE-2026-42535 affects the following packages: apache (Bitnami). Ecosystems affected: Bitnami.

How do I fix CVE-2026-42535?

Update apache to 2.4.68 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-42535 is resolved across your whole dependency graph.

How do I detect CVE-2026-42535 in my Bitnami dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for apache, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-42535 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-42535 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-42535 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-42535?

CVE-2026-42535 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 52th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-42535?

CVE-2026-42535 is classified as CWE-668 (CWE-668). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-42535 published, and has it been updated?

CVE-2026-42535 was published on June 10, 2026 and was last updated on September 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Bitnami

Not in CISA KEV

CVE-2026-42535 — apache

CVE-2026-42535 is a CWE-668 vulnerability in apache. A fix is available for apache — see the affected versions and patch details below.

Apache HTTP Server: mod_dav_fs protected directory access

Published

Jun 10, 2026

Updated

Sep 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-42535.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs52th percentile — riskier than 52% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

📦apache

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Bitnami packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Bitnami	`apache`	all versions	2.4.68

Affected Products

1 product · 1 configurations

Application

http serverapache

< 2.4.68

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for apache, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update apache to 2.4.68 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-42535 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
JBoss Core Services for RHEL 8	`jbcs-httpd24-httpd-0:2.4.62-16.el8jbcs`	RHSA-2026:56868
Red Hat Enterprise Linux 10	`httpd-0:2.4.63-13.el10_2.4`	RHSA-2026:34109
Red Hat Enterprise Linux 9	`httpd-0:2.4.62-13.el9_8.5`	RHSA-2026:41906
Red Hat Hardened Images	`httpd-main-2.4.68-1.hum1`	RHSA-2026:25042
Red Hat Insights proxy 1.5	`insights-proxy/insights-proxy-container-rhel9:1786433656`	RHSA-2026:53371

UbuntuCRITICAL

USN-8516-1Ubuntu USN-8571-1Ubuntu

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2026-42535 in your dependencies?

Find it across Bitnami, including transitive dependencies.

Scan my dependencies How O3 SCA works