plone.app.event provides the event content type for Plone. Prior to versions 5.2.4 and 6.0.1, the iCalendar import in src/plone/app/event/ical/importer.py accepts insufficiently restricted calendar and event URLs, does not adequately bound downloaded bytes or imported events, and commits work per event. A logged-in editor can make the server request internal network resources or local calendar files, exhaust resources and take the site offline, and store a malicious event URL that executes script in another user's browser. The fix restricts accepted URLs, applies MAXIMUM_ICAL_IMPORT_SIZE_BYTES and MAXIMUM_ICAL_IMPORT_EVENTS limits, uses transaction savepoints, and validates event URLs. This issue is fixed in versions 5.2.4 and 6.0.1.
CVE-2026-55247
This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.1
- EG Score
- 9.1(medium)
- EG Risk
- 41(Track)EG Risk 41/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 computedSeverity91% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 28%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
September 9, 2026
Advisory Details (3)
Auto-updated Sep 15, 2026Denial of service via iCalendar import · Advisory · plone/plone.app.event · GitHub
https://github.com/plone/plone.app.event/security/advisories/GHSA-r82h-mqw3-fc56commit 4de5eb3ea9e4 (plone/plone.app.event)
Fix landed in plone/plone.app.event commit 4de5eb3ea9e4 — awaiting tagged release
https://github.com/plone/plone.app.event/commit/4de5eb3ea9e4f7f1781622e6d64fc086629d1437commit 1e3c83c15a24 (plone/plone.app.event)
Fix landed in plone/plone.app.event commit 1e3c83c15a24 — awaiting tagged release
https://github.com/plone/plone.app.event/commit/1e3c83c15a24d1a789cdb012593505bc5620e28eVendor Advisories for CVE-2026-55247(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| plone-app-event | 6.0.0, 6.0.0a1, 6.0.0a2 | 6.0.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× 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.
- 2026-09-18 21:49 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 20:50 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 18:58 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEG score recompute
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 03:47 UTCEG score recompute
- 2026-09-15 03:11 UTCEPSS rescore
- 2026-09-13 17:03 UTCEG score recompute
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 16:04 UTCEG score recompute
- 2026-09-11 15:01 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 10:51 UTCEG score recompute
- 2026-09-10 09:43 UTCEG score recompute
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-09 00:26 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 19:11 UTCEG score recompute
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 17:29 UTCEG score recompute
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-05 16:25 UTCEG score recompute
Show 17 moreShow fewer
- 2026-09-04 15:08 UTCEG score recompute
- 2026-09-04 06:46 UTCEG score recompute
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 20:23 UTCEG score recompute
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 16:37 UTCEG score recompute
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 08:09 UTCEG score recompute
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 19:31 UTCEG score recompute
- 2026-08-31 18:57 UTCEG score recompute
- 2026-08-30 22:32 UTCEG score recompute
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:42 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 20:25 UTCEG score recompute
- 2026-08-28 19:10 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-400
Frequently asked(5)
What is CVE-2026-55247?
When was CVE-2026-55247 disclosed?
Is CVE-2026-55247 actively exploited?
What is the CVSS score of CVE-2026-55247?
How do I remediate CVE-2026-55247?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55247
Is Your Infrastructure Affected by CVE-2026-55247?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.