CVE-2026-73571

MEDIUMNVD 4.34.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 4.3 under NVD CVSS v3. EPSS exploit probability: 0.9% (60th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 3.1 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-08-13) is not newer than that change (2026-08-28), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Weaponized

Also known asEUVD-2026-58070 (ENISA EUVD) · GHSA-p856-mgqw-j9rq (GitHub Security Advisories)Source: ENISA EUVD

4.3EG
EchelonGraph verdictPlan mitigationNo fix is confirmed yet: check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule (the SSVC decision on this page).
  • Public exploit code is available (Metasploit)
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 4.3Exploit: MetasploitExposed services: Not assessed

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

The CVE record's CNA (MITRE Corporation) lists Zimbra Collaboration versions before 10.1.17 as affected. No release containing a fix is confirmed on record.

An authorization bypass vulnerability exists in Zimbra Collaboration (ZCS) before 10.1.17 due to improper authorization validation in delegated email sending functionality. An authenticated attacker can send specially crafted SOAP requests to impersonate another user and send emails without possessing the required delegation or send-as permissions. This occurs in the SaveDraftRequest SOAP handler.

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity43% × 45%
Impact severity (EG Severity): CVSS 4.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation65% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.
EPSS PROB
0.9%
EPSS %ILE
60th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.3): severity, escalated by confirmed exploitation. This CVE's 4.3 is its impact severity (EG Severity), not escalated.

EG Severity
4.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 13, 2026

Last Modified

August 28, 2026

Advisory Details (2)

Auto-updated Aug 28, 2026
No fix on record yet.
Web page

Zimbra Security Advisories - Zimbra :: Tech Center

https://wiki.zimbra.com/wiki/Zimbra_Security_Advisories
Web page

Security Center - Zimbra :: Tech Center

https://wiki.zimbra.com/wiki/Security_Center

Vendor Advisories for CVE-2026-73571(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 / 31× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 181 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 81 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-21 16:41 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  2. 2026-11-20 16:38 UTCEPSS rescoreEPSS 0.6% · 51st percentile
  3. 2026-11-19 16:35 UTCEPSS rescoreEPSS 0.6% · 51st percentile
  4. 2026-11-18 16:35 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  5. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  6. 2026-11-16 16:52 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  7. 2026-11-15 17:02 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  8. 2026-11-14 16:41 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  9. 2026-11-13 16:57 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  10. 2026-11-13 16:55 UTCEchelonGraph re-scored
  11. 2026-11-13 16:55 UTCGHSA enrichmentGHSA-p856-mgqw-j9rq · GitHub severity LOW · GitHub CVSS 3.1
  12. 2026-11-13 16:37 UTCEchelonGraph re-scored
  13. 2026-11-13 16:37 UTCGHSA enrichmentGHSA-p856-mgqw-j9rq · GitHub severity LOW · GitHub CVSS 3.1
  14. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  15. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  16. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  17. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  18. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  19. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  20. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  21. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  22. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  23. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  24. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  25. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
Show 75 more
  1. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  2. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  3. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  4. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  5. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  6. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  7. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  8. 2026-10-25 14:05 UTCEchelonGraph re-scored
  9. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  10. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  11. 2026-10-22 19:01 UTCEchelonGraph re-scored
  12. 2026-10-22 19:01 UTCGHSA enrichmentGHSA-p856-mgqw-j9rq · GitHub severity LOW · GitHub CVSS 3.1
  13. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  14. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  15. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  16. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  17. 2026-10-18 03:15 UTCEchelonGraph re-scored
  18. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  19. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  20. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  21. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  22. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  23. 2026-10-12 15:40 UTCEchelonGraph re-scored
  24. 2026-10-11 19:26 UTCEchelonGraph re-scored
  25. 2026-10-11 16:42 UTCEchelonGraph re-scored
  26. 2026-10-11 14:01 UTCEchelonGraph re-scored
  27. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  28. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  29. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  30. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  31. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  32. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  33. 2026-10-06 13:22 UTCEchelonGraph re-scored
  34. 2026-10-06 13:22 UTCGHSA enrichmentGHSA-p856-mgqw-j9rq · GitHub severity LOW · GitHub CVSS 3.1
  35. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  36. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  37. 2026-10-04 22:19 UTCGHSA enrichmentGHSA-p856-mgqw-j9rq · GitHub severity LOW · GitHub CVSS 3.1
  38. 2026-10-03 19:49 UTCEchelonGraph re-scored
  39. 2026-10-03 19:48 UTCGHSA enrichmentGHSA-p856-mgqw-j9rq · GitHub severity LOW · GitHub CVSS 3.1
  40. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  41. 2026-10-02 07:33 UTCEchelonGraph re-scored
  42. 2026-10-02 07:33 UTCGHSA enrichmentGHSA-p856-mgqw-j9rq · GitHub severity LOW · GitHub CVSS 3.1
  43. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  44. 2026-09-30 21:47 UTCEchelonGraph re-scored
  45. 2026-09-30 21:47 UTCGHSA enrichmentGHSA-p856-mgqw-j9rq · GitHub severity LOW · GitHub CVSS 3.1
  46. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  47. 2026-09-29 07:18 UTCEchelonGraph re-scored
  48. 2026-09-29 07:18 UTCGHSA enrichmentGHSA-p856-mgqw-j9rq · GitHub severity LOW · GitHub CVSS 3.1
  49. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  50. 2026-09-28 08:32 UTCEchelonGraph re-scored
  51. 2026-09-28 08:32 UTCGHSA enrichmentGHSA-p856-mgqw-j9rq · GitHub severity LOW · GitHub CVSS 3.1
  52. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  53. 2026-09-27 09:44 UTCEchelonGraph re-scored
  54. 2026-09-27 09:44 UTCGHSA enrichmentGHSA-p856-mgqw-j9rq · GitHub severity LOW · GitHub CVSS 3.1
  55. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  56. 2026-09-25 03:33 UTCEchelonGraph re-scored
  57. 2026-09-25 03:33 UTCGHSA enrichmentGHSA-p856-mgqw-j9rq · GitHub severity LOW · GitHub CVSS 3.1
  58. 2026-09-23 20:49 UTCEchelonGraph re-scored
  59. 2026-09-23 20:49 UTCGHSA enrichmentGHSA-p856-mgqw-j9rq · GitHub severity LOW · GitHub CVSS 3.1
  60. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  61. 2026-09-22 21:00 UTCEchelonGraph re-scored
  62. 2026-09-22 21:00 UTCGHSA enrichmentGHSA-p856-mgqw-j9rq · GitHub severity LOW · GitHub CVSS 3.1
  63. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  64. 2026-09-21 20:45 UTCGHSA enrichmentGHSA-p856-mgqw-j9rq · GitHub severity LOW · GitHub CVSS 3.1
  65. 2026-09-20 21:55 UTCEchelonGraph re-scored
  66. 2026-09-20 21:55 UTCGHSA enrichmentGHSA-p856-mgqw-j9rq · GitHub severity LOW · GitHub CVSS 3.1
  67. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  68. 2026-09-19 23:10 UTCEchelonGraph re-scored
  69. 2026-09-19 23:10 UTCGHSA enrichmentGHSA-p856-mgqw-j9rq · GitHub severity LOW · GitHub CVSS 3.1
  70. 2026-09-18 23:14 UTCEchelonGraph re-scored
  71. 2026-09-18 23:14 UTCGHSA enrichmentGHSA-p856-mgqw-j9rq · GitHub severity LOW · GitHub CVSS 3.1
  72. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  73. 2026-09-18 00:29 UTCEchelonGraph re-scored
  74. 2026-09-18 00:29 UTCGHSA enrichmentGHSA-p856-mgqw-j9rq · GitHub severity LOW · GitHub CVSS 3.1
  75. 2026-09-16 23:59 UTCEchelonGraph re-scored

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Metasploit module). No fix is confirmed yet, so defenders should restrict or isolate affected systems accordingly until one is published.

  • Metasploitauxiliary/admin/http/zimbra_email_impersonation✓ verified
    Recorded Nov 13, 2026

    Zimbra SaveDraftRequest Email Impersonation

    Open source ↗

Frequently asked(5)

What is CVE-2026-73571?
CVE-2026-73571 is a medium-severity vulnerability; its CVE record was published on August 13, 2026. An authorization bypass vulnerability exists in Zimbra Collaboration (ZCS) before 10.1.17 due to improper authorization validation in delegated email sending functionality. An authenticated attacker can send specially crafted SOAP requests to impersonate another user and send emails without…
When was the CVE record for CVE-2026-73571 published?
The CVE record for CVE-2026-73571 was published on August 13, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 28, 2026; the record at its source may have been updated since.
Is CVE-2026-73571 actively exploited?
CVE-2026-73571 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (60th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73571?
CVE-2026-73571 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-73571?
No fix for CVE-2026-73571 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (MITRE Corporation) lists Zimbra Collaboration versions before 10.1.17 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-73571 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-73571?

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