Apache HTTP Server: mod_dav_fs property database read access
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.53% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: azl3 httpd 2.4.68-1 on Azure Linux 3.0 2.4.69-1.
Low priority for now. Upgrade to azl3 httpd 2.4.68-1 on Azure Linux 3.0 2.4.69-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Internal state files accessible to external parties in mod_dav_fs in Apache Software Foundation Apache HTTP Server before 2.4.69 on all platforms allows a remote client to read WebDAV dead properties of resources it cannot author via a GET request for the .DAV state directory This issue affects Apache HTTP Server: from 2.4.0 through 2.4.68.
- Published
- Oct 1, 2026
- Updated
- Oct 5, 2026
- EPSS
- 0.5% · 44th percentile
- CWE
- CWE-552
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| apache | http server | cpe:2.3:a:apache:http_server |
Using http server? Add it to your stack and be the first to know about CVEs like this one. (Apache HTTP)
Is Apache HTTP Server on your server exposed to the internet?
The free port scanner finds the open ports on your server and matches the service versions it can read against known vulnerabilities. No account needed.
Run a port scanAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apache http server2.4.0 and later · before 2.4.69
Versions reported by the vendor
Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.
Apache Software Foundation Apache HTTP Server
- 2.4.0 and later · up to and including 2.4.68affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.21 | apache2 | before 2.4.69-r0 | 2.4.69-r0 |
| Debian:12 | apache2 | from 0 | — |
| Debian:13 | apache2 | before 2.4.69-1~deb13u1 | 2.4.69-1~deb13u1 |
| Debian:14 | apache2 | before 2.4.69-1 | 2.4.69-1 |
| Red Hat:hummingbird:1 | httpd | before 0:2.4.69-1.hum1 | 0:2.4.69-1.hum1 |
| Red Hat:hummingbird:1 | httpd-core | before 0:2.4.69-1.hum1 | 0:2.4.69-1.hum1 |
| Red Hat:hummingbird:1 | httpd-devel | before 0:2.4.69-1.hum1 | 0:2.4.69-1.hum1 |
| Red Hat:hummingbird:1 | httpd-filesystem | before 0:2.4.69-1.hum1 | 0:2.4.69-1.hum1 |
| Red Hat:hummingbird:1 | httpd-manual | before 0:2.4.69-1.hum1 | 0:2.4.69-1.hum1 |
| Red Hat:hummingbird:1 | httpd-tools | before 0:2.4.69-1.hum1 | 0:2.4.69-1.hum1 |
| Red Hat:hummingbird:1 | mod_ldap | before 0:2.4.69-1.hum1 | 0:2.4.69-1.hum1 |
| Red Hat:hummingbird:1 | mod_lua | before 0:2.4.69-1.hum1 | 0:2.4.69-1.hum1 |
| Red Hat:hummingbird:1 | mod_proxy_html | before 0:2.4.69-1.hum1 | 0:2.4.69-1.hum1 |
| Red Hat:hummingbird:1 | mod_session | before 0:2.4.69-1.hum1 | 0:2.4.69-1.hum1 |
| Red Hat:hummingbird:1 | mod_ssl | before 0:2.4.69-1.hum1 | 0:2.4.69-1.hum1 |
Same product
apache: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-42013Path Traversal and Remote Code Execution in Apache HTTP Server 2.4.49 and 2.4.50 (incomplete fix of CVE-2021-41773)KEV99Now
- CVE-2021-41773Path traversal and file disclosure vulnerability in Apache HTTP Server 2.4.49KEV99Now
- CVE-2024-38475Apache HTTP Server weakness in mod_rewrite when first segment of substitution matches filesystem path.KEV96Now
Published before and after this one in the same product
- ← EarlierCVE-2026-56449Oct 1, 2026 · Apache HTTP Server: mod_proxy_html: crash in dump_content30Monitor
- ← EarlierCVE-2026-57941Oct 1, 2026 · Apache HTTP Server: mod_http2 use-after-free / wild write via shared session->bbtmp re-entrancy39Monitor
- Later →CVE-2026-59685Oct 1, 2026 · Apache HTTP Server: Out-of-Bounds Write in ap_directory_walk() Canonical-Name Rewrite on CASE_BLIND_FILESYSTEM30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| azl3 httpd 2.4.68-1 on Azure Linux 3.0 | 2.4.69-1 · Release Notes | Microsoft (MSRC) |
| alpine:apache2 | 2.4.69-r0 · Alpine:v3.21 | Package registry (OSV) |
| debian:apache2 | 2.4.69-1 · Debian:14 | Package registry (OSV) |
| debian:apache2 | 2.4.69-1~deb13u1 · Debian:13 | Package registry (OSV) |
| red hat:httpd | 0:2.4.69-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:httpd-core | 0:2.4.69-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:httpd-devel | 0:2.4.69-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:httpd-filesystem | 0:2.4.69-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:httpd-manual | 0:2.4.69-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:httpd-tools | 0:2.4.69-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:mod_ldap | 0:2.4.69-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:mod_lua | 0:2.4.69-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:mod_proxy_html | 0:2.4.69-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:mod_session | 0:2.4.69-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:mod_ssl | 0:2.4.69-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recorded+2 d
- TodayOct 23, 2026+22 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- 이지웅 (kimchunbok)finder
- sungbyeongchanfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-552 · Files or Directories Accessible to External PartiesCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
- OS Credential DumpingT1003
- Data from Network Shared DriveT1039
- Automated CollectionT1119
- Data from Information RepositoriesT1213
- Data from Cloud Storage ObjectT1530
- Unsecured Credentials: Credentials in FilesT1552.001
- Unsecured Credentials: Bash HistoryT1552.003
- Unsecured Credentials: Private KeysT1552.004
- Unsecured Credentials: Group Policy PreferencesT1552.006
- Credentials from Password StoresT1555
- Data from Configuration RepositoryT1602
Change log
- Fix✗ → ✓
- CVSS— → 5.3
- Severity— → medium
- SSVC exploitation— → none
- Exploit maturity— → none
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.