CVE-2026-55509

HIGHPre-NVD 8.88.8
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
Trending — 3 sources updated this weekElevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

WsgiDAV is a generic and extendable WebDAV server based on WSGI. Prior to 4.3.5, the sample MySQLBrowserProvider in wsgidav/samples/mysql_dav_provider.py concatenates the record key parsed from a request URL directly into SQL WHERE clauses. The affected _exists_record_by_primary_key, _get_field_by_primary_key, and _get_record_by_primary_key methods are part of a shipped example provider that is not enabled by default. An attacker who can access a share explicitly configured with this non-default provider can inject SQL through a normal GET request; anonymously exposed read shares permit a status-code oracle and extraction of arbitrary data reachable by the configured MySQL account. This issue is fixed in version 4.3.5.

CVSS v3
8.8
EG Score
8.8(low)
EG Risk
71(Attend)
EG Risk 71/100SSVC: Attend

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
Severity88% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

August 28, 2026

Last Modified

August 28, 2026

Advisory Details (4)

Auto-updated Aug 28, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

Blind SQL injection in WsgiDAV MySQL provider · Advisory · mar10/wsgidav · GitHub

https://github.com/mar10/wsgidav/security/advisories/GHSA-p6gw-4frg-j7jw
github_release Patch Available

v4.3.5

Patch available: mar10/wsgidav v4.3.5

https://github.com/mar10/wsgidav/releases/tag/v4.3.5
github_commit Patch Available

commit 6f35776c9188 (mar10/wsgidav)

Patch available: mar10/wsgidav v4.3.5 (contains commit 6f35776c9188)

https://github.com/mar10/wsgidav/commit/6f35776c9188f130ab044ce557015d51aaa83500
generic

wsgidav/CHANGELOG.md at master · mar10/wsgidav · GitHub

https://github.com/mar10/wsgidav/blob/master/CHANGELOG.md#435--2026-06-27

Vendor Advisories for CVE-2026-55509(1)

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

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 6× 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.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-28 22:45 UTCEG score recompute
  3. 2026-08-28 22:09 UTCEG score recompute
  4. 2026-08-28 20:24 UTCEG score recompute▲ 8.80
  5. 2026-08-28 20:24 UTCNVD updateCVSS v3 → 8.8 · CVSS v4 → 8.8
  6. 2026-08-28 19:11 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-55509?
CVE-2026-55509 is a high vulnerability published on August 28, 2026. WsgiDAV is a generic and extendable WebDAV server based on WSGI. Prior to 4.3.5, the sample MySQLBrowserProvider in wsgidav/samples/mysqldavprovider.py concatenates the record key parsed from a request URL directly into SQL WHERE clauses. The affected existsrecordbyprimarykey, getfieldbyprimarykey,…
When was CVE-2026-55509 disclosed?
CVE-2026-55509 was first published in the National Vulnerability Database on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55509 actively exploited?
CVE-2026-55509 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 67.2% of all scored CVEs.
What is the CVSS score of CVE-2026-55509?
CVE-2026-55509 has a CVSS v3 base score of 8.8 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-55509?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55509, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-55509

Explore →

Is Your Infrastructure Affected by CVE-2026-55509?

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

Start Free Scan →Browse All CVEs