CVE-2026-52681

LOWPre-NVD 3.13.1
EchelonGraph scoreHIGH confidence

Score 3.1 from GitHub Security Advisory (severity: LOW) published 2026-08-28. a secondary CVSS source baseline 3.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
3.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.1Exploit: None knownExposed: 0

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

Sieve CPU resource usage is tracked in the compiled script, so an attacker that has valid credentials can reset the accounting by repeatedly changing the active script. Compiled script files are also not removed when a script is deleted or renamed. The configured Sieve CPU limit can be bypassed, allowing sustained CPU consumption, and the leftover files increase disk consumption. Both can cause degradation of service for mail delivery. Monitor system for abnormal CPU usage and disk consumption. Update to non-vulnerable version. No publicly available exploits are known.

CVSS v3
3.1
EG Score
3.1(high)
EG Risk
14(Track)
EG Risk 14/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
Severity31% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

August 28, 2026

Last Modified

September 3, 2026

Vendor Advisories for CVE-2026-52681(1)

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

Affected Packages

(5 across 5 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
dovecot2.4.5-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
dovecot2.4.5-r0
Debian:12(1)
PackageVulnerable rangeFixed inDependents
dovecot1:2.3.19.1+dfsg1-2.1 ... 1:2.4.5+dfsg1-2 (42 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
dovecot1:2.4.1+dfsg1-6 ... 1:2.4.5+dfsg1-2 (20 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
dovecot1:2.4.1+dfsg1-6 ... 1:2.4.5+dfsg1-2 (14 versions)

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-52681?
CVE-2026-52681 is a low vulnerability published on August 28, 2026. Sieve CPU resource usage is tracked in the compiled script, so an attacker that has valid credentials can reset the accounting by repeatedly changing the active script. Compiled script files are also not removed when a script is deleted or renamed. The configured Sieve CPU limit can be bypassed,…
When was CVE-2026-52681 disclosed?
CVE-2026-52681 was first published in the National Vulnerability Database on August 28, 2026, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52681 actively exploited?
CVE-2026-52681 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 82.6% of all scored CVEs.
What is the CVSS score of CVE-2026-52681?
CVE-2026-52681 has a CVSS v3 base score of 3.1 (NVD).
How do I remediate CVE-2026-52681?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52681, 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-52681

Explore →

Is Your Infrastructure Affected by CVE-2026-52681?

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