CVE-2026-57149

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-23. A secondary CVSS source baseline 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-84802 (ENISA EUVD) · GHSA-rr49-f9g6-c9r5 (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
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.6%CVSS: 9.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

plone.app.portlets.portlets provides a Plone-specific user interface for plone.portlets, as well as a standard set of portlets that ship with Plone. Starting in version 5.0.0 and prior to versions 5.0.8, 6.0.4, and 7.0.2, the Classic portlet (plone.app.portlets.portlets.classic) used its user-supplied template/macro fields to build a TALES path expression that was then evaluated by the TAL path() helper. Because the value was interpreted as a full TALES expression, a user able to add or edit a Classic portlet could supply a crafted value that escapes simple path traversal and is evaluated as arbitrary code. This is exploitable by any authenticated user who can configure a Classic portlet - which, with the default role map, includes regular users on their personal dashboard. The result is code execution in the context of the Plone process, i.e. a privilege escalation across the trust boundary between an authenticated web user and the server-side process. The problem has been patched in plone.app.portlets 5.0.8, 6.0.4, and 7.0.2. Some workarounds are available. Restrict who can manage portlets: remove the plone.app.portlets.ManageOwnPortlets permission from untrusted roles, and limit Manage portlets to trusted administrators (usually this is already restricted to the Manager and Site Administrator roles). Where the Classic portlet is not needed, unregister it so it cannot be added. This would need to be done by editing a portlets.xml in your own code. One may also effectively disable showing the classic portlet by customising its template. In the Zope Management Interface go to the portal_view_customizations tool, locate the classic.pt template and click it. Click the Customize button. Remove all text and replace it with The classic portlet was disabled.. (This is not a recommended way of customizing a template, but in this case it is quite effective.)

CVSS v3
9.9
EG Score
9.9CRITICALmedium 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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.6%
EPSS %ILE
50th
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 (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

September 22, 2026

Last Modified

September 23, 2026

Advisory Details (1)

Auto-updated Oct 30, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Remote Code Execution via TALES Injection · Advisory · plone/plone.app.portlets · GitHub

https://github.com/plone/plone.app.portlets/security/advisories/GHSA-rr49-f9g6-c9r5

Vendor Advisories for CVE-2026-57149(1)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipplone.app.portlets @ 7.0.2 (fixes >= 7.0.0, <= 7.0.1)—ghsa
pipplone.app.portlets @ 6.0.4 (fixes >= 6.0.0, <= 6.0.3)—ghsa
pipplone.app.portlets @ 5.0.8 (fixes >= 5.0.0, <= 5.0.7)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
plone-app-portlets5.0.0 ... 7.0.1 (14 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
  • 5.0.0 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 17× in last 7d / 67× 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-11-02 01:32 UTCEG score recompute
  2. 2026-11-02 01:32 UTCGHSA enrichmentGHSA-rr49-f9g6-c9r5 · GitHub severity CRITICAL · GitHub CVSS 9.9
  3. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  4. 2026-11-01 07:42 UTCGHSA enrichmentGHSA-rr49-f9g6-c9r5 · GitHub severity CRITICAL · GitHub CVSS 9.9
  5. 2026-11-01 07:42 UTCEG score recompute
  6. 2026-11-01 00:37 UTCEG score recompute
  7. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  8. 2026-10-30 23:42 UTCEG score recompute
  9. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  10. 2026-10-29 22:47 UTCEG score recompute
  11. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  12. 2026-10-28 21:52 UTCEG score recompute
  13. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  14. 2026-10-27 20:58 UTCEG score recompute
  15. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  16. 2026-10-26 20:03 UTCEG score recompute
  17. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  18. 2026-10-25 17:10 UTCEG score recompute
  19. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  20. 2026-10-25 14:17 UTCEG score recompute
  21. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  22. 2026-10-24 16:15 UTCEG score recompute
  23. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  24. 2026-10-23 15:18 UTCEG score recompute
  25. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
Show 66 more
  1. 2026-10-22 14:22 UTCEG score recompute
  2. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  3. 2026-10-21 13:26 UTCEG score recompute
  4. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  5. 2026-10-20 12:28 UTCEG score recompute
  6. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  7. 2026-10-19 11:31 UTCEG score recompute
  8. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  9. 2026-10-18 03:29 UTCEG score recompute
  10. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  11. 2026-10-17 08:16 UTCEG score recompute
  12. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  13. 2026-10-16 07:20 UTCEG score recompute
  14. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  15. 2026-10-15 06:15 UTCEG score recompute
  16. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  17. 2026-10-14 01:54 UTCEG score recompute
  18. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  19. 2026-10-12 22:10 UTCEG score recompute
  20. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  21. 2026-10-12 15:54 UTCEG score recompute
  22. 2026-10-11 19:37 UTCEG score recompute
  23. 2026-10-11 16:52 UTCEG score recompute
  24. 2026-10-11 14:15 UTCEG score recompute
  25. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  26. 2026-10-11 11:22 UTCEG score recompute
  27. 2026-10-10 23:24 UTCEG score recompute
  28. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  29. 2026-10-09 20:30 UTCEG score recompute
  30. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  31. 2026-10-08 21:03 UTCEG score recompute
  32. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  33. 2026-10-08 02:30 UTCEG score recompute
  34. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  35. 2026-10-06 15:56 UTCEG score recompute
  36. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  37. 2026-10-05 20:45 UTCEG score recompute
  38. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  39. 2026-10-05 01:29 UTCEG score recompute
  40. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  41. 2026-10-03 14:48 UTCEG score recompute
  42. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  43. 2026-10-02 19:33 UTCEG score recompute
  44. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  45. 2026-10-02 00:05 UTCEG score recompute
  46. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  47. 2026-09-30 16:46 UTCEG score recompute
  48. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  49. 2026-09-29 18:17 UTCEG score recompute
  50. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  51. 2026-09-28 22:11 UTCEG score recompute
  52. 2026-09-28 14:29 UTCEG score recompute
  53. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  54. 2026-09-27 15:20 UTCEG score recompute
  55. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  56. 2026-09-26 16:16 UTCEG score recompute
  57. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  58. 2026-09-26 00:44 UTCEG score recompute
  59. 2026-09-24 17:59 UTCEG score recompute
  60. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  61. 2026-09-23 18:25 UTCEG score recompute
  62. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  63. 2026-09-22 20:32 UTCEG score recompute
  64. 2026-09-22 19:24 UTCEG score recompute
  65. 2026-09-22 19:08 UTCEG score recomputeFirst assessed: 9.9 CRITICAL
  66. 2026-09-22 19:08 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Same product

1 shown

PyPI:plone-app-portlets

Frequently asked(5)

What is CVE-2026-57149?
CVE-2026-57149 is a critical-severity vulnerability; its CVE record was published on September 22, 2026. plone.app.portlets.portlets provides a Plone-specific user interface for plone.portlets, as well as a standard set of portlets that ship with Plone. Starting in version 5.0.0 and prior to versions 5.0.8, 6.0.4, and 7.0.2, the Classic portlet (plone.app.portlets.portlets.classic) used its…
When was the CVE record for CVE-2026-57149 published?
The CVE record for CVE-2026-57149 was published on September 22, 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 23, 2026; the record at its source may have been updated since.
Is CVE-2026-57149 actively exploited?
CVE-2026-57149 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-57149?
CVE-2026-57149 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-57149?
A fix for CVE-2026-57149 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-57149 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-57149

Explore →

Is Your Infrastructure Affected by CVE-2026-57149?

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

Book a Demo →Browse All CVEs