CVE-2026-6879

LOWPre-NVD 2.02.0—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 72% of all CVEs by exploit prediction. 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: epss, secondary
Trending — 4 sources updated this week
2.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.0Exploit: None knownExposed: 0

A fix is available — apply it.

Element.findall() and fully-consumed Element.iterfind() exhibit O(n^2) time complexity when using XPath index predicates (e.g. [1], [last()], [last()-N]) on XML documents with many same-tag siblings. Element.find() is only affected when the first match is near the end  of the sibling list, such as with [last()] or [last()-N];  .//item[1] short-circuits after the first match.

CVSS v3
2.0
EG Score
2.0(medium)
EG Risk
9(Track)
EG Risk 9/100SSVC: Track

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
Severity20% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

July 28, 2026

Last Modified

August 13, 2026

References (10)

Vendor Advisories for CVE-2026-6879(7)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpython3-14-main-3.14.6-2.2.hum12026-07-29redhat
redhatpython3-10-main-3.10.20-3.2.hum12026-07-29redhat
redhatpython3-11-main-3.11.15-5.5.hum12026-07-29redhat
redhatpython3-13-main-3.13.14-1.7.hum12026-07-29redhat
redhatpython3-12-main-3.12.13-3.8.hum12026-07-29redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(10 across 4 ecosystems)
Debian:11(3)
PackageVulnerable rangeFixed inDependents
pypy37.3.10+dfsg-1 ... 7.3.9+dfsg-5 (53 versions)——
python2.72.7.18-10 ... 2.7.18-9 (10 versions)——
python3.93.9.10-1 ... 3.9.9-4 (29 versions)——
Debian:14(3)
PackageVulnerable rangeFixed inDependents
pypy37.3.19+dfsg-2 ... 7.3.23+dfsg-1 (11 versions)——
python3.133.13.11-1 ... 3.13.9-1 (8 versions)——
python3.143.14.0-1 ... 3.14.6-1 (24 versions)——
Debian:12(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.11+dfsg-2 ... 7.3.23+dfsg-1 (29 versions)——
python3.113.11.2-6 ... 3.11.9-1 (28 versions)——
Debian:13(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.19+dfsg-2 ... 7.3.23+dfsg-1 (11 versions)——
python3.133.13.11-1 ... 3.13.9-1 (12 versions)——

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 21× in last 7d / 59× 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-15 01:31 UTCEPSS rescore
  2. 2026-08-13 22:00 UTCEPSS rescore
  3. 2026-08-13 01:23 UTCEG score recompute
  4. 2026-08-13 01:23 UTCVendor advisory
  5. 2026-08-13 01:23 UTCGHSA enrichment
  6. 2026-08-13 00:41 UTCEG score recompute
  7. 2026-08-13 00:41 UTCVendor advisory
  8. 2026-08-13 00:41 UTCGHSA enrichment
  9. 2026-08-12 13:51 UTCEPSS rescore
  10. 2026-08-11 01:22 UTCEG score recompute
  11. 2026-08-11 01:22 UTCVendor advisory
  12. 2026-08-11 01:22 UTCGHSA enrichment
  13. 2026-08-11 00:34 UTCEG score recompute
  14. 2026-08-11 00:34 UTCVendor advisory
  15. 2026-08-11 00:34 UTCGHSA enrichment
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-09 13:47 UTCEPSS rescore
  18. 2026-08-09 06:50 UTCEG score recompute
  19. 2026-08-09 06:50 UTCVendor advisory
  20. 2026-08-09 06:50 UTCGHSA enrichment
  21. 2026-08-08 16:37 UTCEPSS rescore
  22. 2026-08-06 13:47 UTCEPSS rescore
  23. 2026-08-06 01:21 UTCEG score recompute
  24. 2026-08-06 01:21 UTCVendor advisory
  25. 2026-08-06 01:21 UTCGHSA enrichment
Show 34 more
  1. 2026-08-06 00:50 UTCEG score recompute
  2. 2026-08-06 00:50 UTCVendor advisory
  3. 2026-08-06 00:50 UTCGHSA enrichment
  4. 2026-08-05 19:17 UTCEPSS rescore
  5. 2026-08-05 19:17 UTCEPSS rescore
  6. 2026-08-05 14:28 UTCEG score recompute
  7. 2026-08-05 14:28 UTCVendor advisory
  8. 2026-08-05 14:28 UTCGHSA enrichment
  9. 2026-08-05 13:49 UTCEG score recompute
  10. 2026-08-05 13:49 UTCVendor advisory
  11. 2026-08-05 13:49 UTCGHSA enrichment
  12. 2026-08-05 01:19 UTCEG score recompute
  13. 2026-08-05 01:19 UTCGHSA enrichment
  14. 2026-08-05 00:51 UTCEG score recompute
  15. 2026-08-05 00:51 UTCGHSA enrichment
  16. 2026-08-04 15:10 UTCEPSS rescore
  17. 2026-08-04 10:39 UTCEPSS rescore
  18. 2026-08-03 10:36 UTCEPSS rescore
  19. 2026-08-03 01:13 UTCEG score recompute
  20. 2026-08-03 01:13 UTCGHSA enrichment
  21. 2026-08-02 02:27 UTCEPSS rescore
  22. 2026-08-01 04:16 UTCEPSS rescore
  23. 2026-07-30 19:45 UTCEG score recompute
  24. 2026-07-30 19:45 UTCGHSA enrichment
  25. 2026-07-30 18:02 UTCEG score recompute
  26. 2026-07-30 18:02 UTCGHSA enrichment
  27. 2026-07-30 16:28 UTCEPSS rescore
  28. 2026-07-30 01:30 UTCEPSS rescore
  29. 2026-07-28 16:40 UTCEG score recompute
  30. 2026-07-28 16:40 UTCGHSA enrichment
  31. 2026-07-28 15:36 UTCEG score recompute
  32. 2026-07-28 15:36 UTCGHSA enrichment
  33. 2026-07-28 14:39 UTCEG score recompute
  34. 2026-07-28 14:38 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-6879?
CVE-2026-6879 is a low vulnerability published on July 28, 2026. Element.findall() and fully-consumed Element.iterfind() exhibit O(n^2) time complexity when using XPath index predicates (e.g. [1], [last()], [last()-N]) on XML documents with many same-tag siblings. Element.find() is only affected when the first match is near the end of the sibling list, such as…
When was CVE-2026-6879 disclosed?
CVE-2026-6879 was first published in the National Vulnerability Database on July 28, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6879 actively exploited?
CVE-2026-6879 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 71.5% of all scored CVEs.
What is the CVSS score of CVE-2026-6879?
CVE-2026-6879 has a CVSS v3 base score of 2.0 (NVD).
How do I remediate CVE-2026-6879?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6879, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-6879

Explore →

Is Your Infrastructure Affected by CVE-2026-6879?

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

Start Free Scan →Browse All CVEs