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.6%, top 55% 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.6%CVSS: 2.0Exploit: None knownExposed services: Not assessed

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.0LOWmedium confidence
EG Risk
9
EG Risk 9/100

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%
Exploitation1% × 40%
Automatability0% × 15%
EPSS PROB
0.6%
EPSS %ILE
45th
KEV
Not listed

Published

July 28, 2026

Last Modified

August 13, 2026

References (10)

Vendor Advisories for CVE-2026-6879(8)

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

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpython3-14-main-3.14.7-1.hum12026-08-13redhat
redhatpython3-13-main-3.13.15-1.hum12026-08-13redhat
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

(11 across 5 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)3.13.15-1—
python3.143.14.0-1 ... 3.14.6-1 (24 versions)3.14.7-1—
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 (13 versions)——
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
python3—3.14.7-r0—

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 10× in last 7d / 42× 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.

Showing the most recent 100 of 131 total refreshes for this CVE.

  1. 2026-09-28 13:52 UTCEPSS rescore
  2. 2026-09-28 03:24 UTCEG score recompute
  3. 2026-09-28 03:24 UTCVendor advisory
  4. 2026-09-28 03:24 UTCGHSA enrichment
  5. 2026-09-27 13:48 UTCEPSS rescore
  6. 2026-09-26 15:59 UTCEPSS rescore
  7. 2026-09-23 17:54 UTCEPSS rescore
  8. 2026-09-22 21:42 UTCEG score recompute
  9. 2026-09-22 21:42 UTCVendor advisory
  10. 2026-09-22 21:42 UTCGHSA enrichment
  11. 2026-09-21 21:09 UTCEPSS rescore
  12. 2026-09-20 20:16 UTCEPSS rescore
  13. 2026-09-18 19:28 UTCEPSS rescore
  14. 2026-09-18 02:06 UTCEG score recompute
  15. 2026-09-18 02:06 UTCVendor advisory
  16. 2026-09-18 02:06 UTCGHSA enrichment
  17. 2026-09-16 14:08 UTCEPSS rescore
  18. 2026-09-16 05:15 UTCEPSS rescore
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-14 07:53 UTCEG score recompute
  21. 2026-09-14 07:53 UTCVendor advisory
  22. 2026-09-14 07:53 UTCGHSA enrichment
  23. 2026-09-12 15:02 UTCEPSS rescore
  24. 2026-09-11 14:53 UTCEPSS rescore
  25. 2026-09-11 02:24 UTCEG score recompute
Show 75 more
  1. 2026-09-11 02:24 UTCVendor advisory
  2. 2026-09-11 02:24 UTCGHSA enrichment
  3. 2026-09-10 09:35 UTCEPSS rescore
  4. 2026-09-08 22:01 UTCEPSS rescore
  5. 2026-09-07 20:55 UTCEG score recompute
  6. 2026-09-07 20:55 UTCVendor advisory
  7. 2026-09-07 20:55 UTCGHSA enrichment
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-05 15:31 UTCEPSS rescore
  11. 2026-09-04 12:02 UTCEG score recompute
  12. 2026-09-04 12:02 UTCVendor advisory
  13. 2026-09-04 12:02 UTCGHSA enrichment
  14. 2026-09-04 05:07 UTCEPSS rescore
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 13:54 UTCEPSS rescore
  17. 2026-09-01 04:40 UTCEPSS rescore
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-29 23:33 UTCEG score recompute
  21. 2026-08-29 23:33 UTCVendor advisory
  22. 2026-08-29 23:33 UTCGHSA enrichment
  23. 2026-08-28 21:42 UTCEPSS rescore
  24. 2026-08-26 14:47 UTCEPSS rescore
  25. 2026-08-25 23:27 UTCEG score recompute
  26. 2026-08-25 23:27 UTCVendor advisory
  27. 2026-08-25 23:27 UTCGHSA enrichment
  28. 2026-08-25 13:49 UTCEPSS rescore
  29. 2026-08-23 00:19 UTCEPSS rescore
  30. 2026-08-22 17:50 UTCEG score recompute
  31. 2026-08-22 17:50 UTCVendor advisory
  32. 2026-08-22 17:50 UTCGHSA enrichment
  33. 2026-08-21 23:49 UTCEPSS rescore
  34. 2026-08-20 22:56 UTCEPSS rescore
  35. 2026-08-19 17:04 UTCEPSS rescore
  36. 2026-08-19 12:21 UTCEG score recompute
  37. 2026-08-19 12:21 UTCVendor advisory
  38. 2026-08-19 12:21 UTCGHSA enrichment
  39. 2026-08-18 13:49 UTCEPSS rescore
  40. 2026-08-18 13:49 UTCEPSS rescore
  41. 2026-08-17 13:47 UTCEPSS rescore
  42. 2026-08-16 14:56 UTCEPSS rescore
  43. 2026-08-16 14:56 UTCEPSS rescore
  44. 2026-08-16 06:52 UTCEG score recompute
  45. 2026-08-16 06:52 UTCVendor advisory
  46. 2026-08-16 06:52 UTCGHSA enrichment
  47. 2026-08-16 02:15 UTCEPSS rescore
  48. 2026-08-15 01:31 UTCEPSS rescore
  49. 2026-08-13 22:00 UTCEPSS rescore
  50. 2026-08-13 01:23 UTCEG score recompute
  51. 2026-08-13 01:23 UTCVendor advisory
  52. 2026-08-13 01:23 UTCGHSA enrichment
  53. 2026-08-13 00:41 UTCEG score recompute
  54. 2026-08-13 00:41 UTCVendor advisory
  55. 2026-08-13 00:41 UTCGHSA enrichment
  56. 2026-08-12 13:51 UTCEPSS rescore
  57. 2026-08-11 01:22 UTCEG score recompute
  58. 2026-08-11 01:22 UTCVendor advisory
  59. 2026-08-11 01:22 UTCGHSA enrichment
  60. 2026-08-11 00:34 UTCEG score recompute
  61. 2026-08-11 00:34 UTCVendor advisory
  62. 2026-08-11 00:34 UTCGHSA enrichment
  63. 2026-08-11 00:00 UTCEPSS rescore
  64. 2026-08-09 13:47 UTCEPSS rescore
  65. 2026-08-09 06:50 UTCEG score recompute
  66. 2026-08-09 06:50 UTCVendor advisory
  67. 2026-08-09 06:50 UTCGHSA enrichment
  68. 2026-08-08 16:37 UTCEPSS rescore
  69. 2026-08-06 13:47 UTCEPSS rescore
  70. 2026-08-06 01:21 UTCEG score recompute
  71. 2026-08-06 01:21 UTCVendor advisory
  72. 2026-08-06 01:21 UTCGHSA enrichment
  73. 2026-08-06 00:50 UTCEG score recompute
  74. 2026-08-06 00:50 UTCVendor advisory
  75. 2026-08-06 00:50 UTCGHSA enrichment

Related CVEs(same product + same vendor + same CWE)

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 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.6% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-6879?
CVE-2026-6879 has a CVSS base score of 2.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-6879?
A fix for CVE-2026-6879 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-6879 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs