How severe is GHSA-qm4x-ch5w-gr62?

No CVSS score has been assigned to GHSA-qm4x-ch5w-gr62 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qm4x-ch5w-gr62?

GHSA-qm4x-ch5w-gr62 affects the following packages: sabre/dav (Packagist), sabre/dav (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-qm4x-ch5w-gr62?

Update sabre/dav to 1.7.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qm4x-ch5w-gr62 is resolved across your whole dependency graph.

How do I detect GHSA-qm4x-ch5w-gr62 in my Packagist dependencies?

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

How do I mitigate GHSA-qm4x-ch5w-gr62 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-qm4x-ch5w-gr62 actively exploited in the wild?

No public exploit code has been indexed for GHSA-qm4x-ch5w-gr62 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 GHSA-qm4x-ch5w-gr62?

GHSA-qm4x-ch5w-gr62 has an EPSS (Exploit Prediction Scoring System) score of 2.2%, placing it in the 83th 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.

When was GHSA-qm4x-ch5w-gr62 published, and has it been updated?

GHSA-qm4x-ch5w-gr62 was published on May 17, 2022 and was last updated on March 31, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

XXE in SabreDAVGHSA-qm4x-ch5w-gr62

Fix: sabre-io/dav@e3f46e0

GHSA-qm4x-ch5w-gr62 is a security vulnerability in sabre/dav. A fix is available for sabre/dav — see the affected versions and patch details below.

Also known asCVE-2014-2055

Published

May 17, 2022

Updated

Mar 31, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

🐘sabre/dav🐘sabre/dav

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

Description

SabreDAV before 1.7.11, as used in ownCloud Server before 5.0.15 and 6.0.x before 6.0.2, allows remote attackers to read arbitrary files, cause a denial of service, or possibly have other impact via an XML External Entity (XXE) attack.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`sabre/dav`	≥ 1.6.0&&< 1.7.11	1.7.11`composer require sabre/dav:^1.7.11`
🐘Packagist	`sabre/dav`	≥ 1.8.0&&< 1.8.9	1.8.9`composer require sabre/dav:^1.8.9`

Affected Products

2 products · 80 configurations

Application

sabredavfruux

≤ 1.7.10

30 versions

1.6.01.6.11.6.21.6.31.6.41.6.51.6.61.6.71.6.81.6.91.6.101.7.0

Application

owncloud serverowncloud

≤ 5.0.14

17 versions

5.0.05.0.15.0.25.0.35.0.45.0.55.0.65.0.75.0.85.0.95.0.105.0.11

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sabre/dav, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update sabre/dav to 1.7.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qm4x-ch5w-gr62 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-qm4x-ch5w-gr62 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works