CVE-2026-55248

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (36th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

plone.app.portlets provides portlets and a Plone-specific user interface for plone.portlets. Prior to 5.0.8, 6.0.4, and 7.0.2, a member who can add an RSS portlet can set its feed URL to a very large response, causing src/plone/app/portlets/portlets/rss.py to download and retain excessive data in memory and deny service. The same RSS URL handling accepts internal hosts, IP addresses, single-word domains, and explicit ports, allowing server-side requests that can probe internal network services and open ports. A malicious feed item can also supply a JavaScript URL that is retained as the item link and can execute script when used by a victim. The affected logic includes _rss_feed_url_validator, _normal_url_validator, RSSFeed._retrieveFeed, RSSFeed._buildItemDict, and the FEED_DATA in-memory cache. This issue is fixed in versions 5.0.8, 6.0.4, and 7.0.2.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/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 (value × EchelonGraph’s weight)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines.

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.

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 28, 2026

Last Modified

September 9, 2026

Advisory Details (5)

Auto-updated Sep 15, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Denial of service via RSS feed portlet · Advisory · plone/plone.app.portlets · GitHub

https://github.com/plone/plone.app.portlets/security/advisories/GHSA-x5g3-w747-2h8q
GitHub commit

commit df5e256baee5 (plone/plone.app.portlets)

Fix landed in plone/plone.app.portlets commit df5e256baee5 — awaiting tagged release

https://github.com/plone/plone.app.portlets/commit/df5e256baee55083cbd6b9a2623675d4cb26b6cd
GitHub commit

commit a3b2c2887165 (plone/plone.app.portlets)

Fix landed in plone/plone.app.portlets commit a3b2c2887165 — awaiting tagged release

https://github.com/plone/plone.app.portlets/commit/a3b2c2887165b308cd915cbb87b8276f90a76680
GitHub commit

commit 9f16b6fb1021 (plone/plone.app.portlets)

Fix landed in plone/plone.app.portlets commit 9f16b6fb1021 — awaiting tagged release

https://github.com/plone/plone.app.portlets/commit/9f16b6fb10211916686c6c346ea174bf517e3fbd
GitHub commit

commit 09da52ef7b29 (plone/plone.app.portlets)

Fix landed in plone/plone.app.portlets commit 09da52ef7b29 — awaiting tagged release

https://github.com/plone/plone.app.portlets/commit/09da52ef7b297daa8e0cfd2361e47c37d9b073ad

Vendor Advisories for CVE-2026-55248(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)
PackageVulnerable rangeFix by version rangeDependents
plone-app-portlets1.0 ... 7.0.1 (158 versions)
  • 7.0.0 up to 7.0.2: fixed in 7.0.2
  • 6.0.0 up to 6.0.4: fixed in 6.0.4
  • every version up to 5.0.8: fixed in 5.0.8
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 59× 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 it from the CNA feed. 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). Most recent first.

  1. 2026-10-14 09:19 UTCEG score recompute
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  3. 2026-10-13 06:37 UTCEG score recompute
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  5. 2026-10-12 15:55 UTCEG score recompute
  6. 2026-10-11 19:39 UTCEG score recompute
  7. 2026-10-11 16:54 UTCEG score recompute
  8. 2026-10-11 14:17 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  11. 2026-10-10 00:49 UTCEG score recompute
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  13. 2026-10-09 02:37 UTCEG score recompute
  14. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  15. 2026-10-08 00:50 UTCEG score recompute
  16. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  17. 2026-10-06 15:55 UTCEG score recompute
  18. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  19. 2026-10-05 20:49 UTCEG score recompute
  20. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  21. 2026-10-04 23:36 UTCEG score recompute
  22. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  23. 2026-10-03 17:38 UTCEG score recompute
  24. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  25. 2026-10-02 18:50 UTCEG score recompute
Show 66 more
  1. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-10-02 00:37 UTCEG score recompute
  3. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  4. 2026-09-30 19:49 UTCEG score recompute
  5. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  6. 2026-09-30 03:49 UTCEG score recompute
  7. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  8. 2026-09-29 01:17 UTCEG score recompute
  9. 2026-09-28 14:23 UTCEG score recompute
  10. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  11. 2026-09-27 14:23 UTCEG score recompute
  12. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  13. 2026-09-26 20:24 UTCEG score recompute
  14. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  15. 2026-09-26 08:03 UTCEG score recompute
  16. 2026-09-24 15:56 UTCEG score recompute
  17. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  18. 2026-09-23 19:52 UTCEG score recompute
  19. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  20. 2026-09-22 18:22 UTCEG score recompute
  21. 2026-09-21 22:20 UTCEG score recompute
  22. 2026-09-20 22:17 UTCEG score recompute
  23. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  24. 2026-09-19 18:13 UTCEG score recompute
  25. 2026-09-18 21:28 UTCEG score recompute
  26. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  27. 2026-09-17 20:50 UTCEG score recompute
  28. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  29. 2026-09-16 15:39 UTCEG score recompute
  30. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  31. 2026-09-16 07:29 UTCEG score recompute
  32. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  33. 2026-09-15 06:46 UTCEG score recompute
  34. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  35. 2026-09-13 17:31 UTCEG score recompute
  36. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  37. 2026-09-12 17:30 UTCEG score recompute
  38. 2026-09-11 17:28 UTCEG score recompute
  39. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  40. 2026-09-11 13:15 UTCEG score recompute
  41. 2026-09-10 13:11 UTCEG score recompute
  42. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  43. 2026-09-09 00:27 UTCEG score recompute
  44. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  45. 2026-09-07 19:02 UTCEG score recompute
  46. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  47. 2026-09-06 16:57 UTCEG score recompute
  48. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  49. 2026-09-05 16:53 UTCEG score recompute
  50. 2026-09-04 16:43 UTCEG score recompute
  51. 2026-09-04 08:41 UTCEG score recompute
  52. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  53. 2026-09-02 15:15 UTCEG score recompute
  54. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  55. 2026-09-01 15:04 UTCEG score recompute
  56. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  57. 2026-09-01 07:01 UTCEG score recompute
  58. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  59. 2026-08-30 22:54 UTCEG score recompute
  60. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  61. 2026-08-30 02:53 UTCEG score recompute
  62. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  63. 2026-08-28 22:44 UTCEG score recompute
  64. 2026-08-28 22:09 UTCEG score recompute
  65. 2026-08-28 20:24 UTCEG score recompute
  66. 2026-08-28 19:10 UTCEG score recomputeFirst assessed: 9.1 CRITICAL

Related CVEs(same product + same CWE)

Same product

1 shown

PyPI:plone-app-portlets

Frequently asked(5)

What is CVE-2026-55248?
CVE-2026-55248 is a critical-severity vulnerability; its CVE record was published on August 28, 2026. plone.app.portlets provides portlets and a Plone-specific user interface for plone.portlets. Prior to 5.0.8, 6.0.4, and 7.0.2, a member who can add an RSS portlet can set its feed URL to a very large response, causing src/plone/app/portlets/portlets/rss.py to download and retain excessive data in…
When was the CVE record for CVE-2026-55248 published?
The CVE record for CVE-2026-55248 was published on August 28, 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 September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-55248 actively exploited?
CVE-2026-55248 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55248?
CVE-2026-55248 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55248?
A fix for CVE-2026-55248 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55248 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-55248

Explore →

Is Your Infrastructure Affected by CVE-2026-55248?

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

Book a Demo →Browse All CVEs