When mail_max_userip_connections is set (default 10) and reached, submission-login can crash with epoll() panic caused by file descriptor handling issues. If running in high-security mode (default for community releases), only the new submission connection gets terminated. If running in high-performance mode (default for Pro releases), all connections handled by the submission-login process will be terminated. The crashes can cause failure for user to send a message, or it can cause duplicate messages to be sent. If TLS is not used (in the backend server processing the submission), duplicate deliveries cannot happen, because the crash can only happen at AUTH stage. Limit the number of connections handled by single submission-login process. This has a performance impact though. Update to non-vulnerable version. No publicly available exploits are known.
CVE-2026-33263
Score 4.3 from GitHub Security Advisory published 2026-08-28. a secondary CVSS source baseline 4.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(high)
- EG Risk
- 19(Track)EG Risk 19/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 computedSeverity43% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 21%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
August 28, 2026
Advisory Details (1)
Auto-updated Aug 28, 2026Vendor Advisories for CVE-2026-33263(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 9× in last 7d / 9× 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.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 18:26 UTCGHSA enrichment
- 2026-08-28 20:21 UTCEG score recompute
- 2026-08-28 20:21 UTCGHSA enrichment
- 2026-08-28 19:45 UTCEG score recompute
- 2026-08-28 19:45 UTCGHSA enrichment
- 2026-08-28 12:23 UTCEG score recompute
- 2026-08-28 11:25 UTCEG score recompute
- 2026-08-28 11:19 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-33263?
When was CVE-2026-33263 disclosed?
Is CVE-2026-33263 actively exploited?
What is the CVSS score of CVE-2026-33263?
How do I remediate CVE-2026-33263?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-33263
Is Your Infrastructure Affected by CVE-2026-33263?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.