CVE-2026-77138

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (52nd 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
Trending — 3 sources updated this week
9.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.3Exploit: None knownExposed 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 (TYPO3 Association) lists TYPO3 Extension "HTML5 Video Player vs. Powermail" versions up to and including 0.2.1 as affected. No release containing a fix is confirmed on record.

The extension fails to safely process untrusted client input of an attacker-controlled cookie directly to PHP's unserialize(). A remote, unauthenticated attacker can supply a crafted serialized payload to trigger PHP Object Injection, leading to Remote Code Execution on the TYPO3 server.

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
57
EG Risk 57/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)
Severity93% × 45%
The EG Score, 9.3 of 10.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.7%
EPSS %ILE
52nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

August 25, 2026

Last Modified

September 28, 2026

Advisory Details (1)

Auto-updated Oct 3, 2026
No fix on record yet.
Web page

TYPO3-EXT-SA-2026-014: Remote Code Execution in extension "HTML5 Video Player vs. Powermail" (html5videoplayer_powermail) - TYPO3 News

https://typo3.org/security/advisory/typo3-ext-sa-2026-014

Vendor Advisories for CVE-2026-77138(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 25× in last 7d / 191× 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.

Showing the most recent 100 of 354 refreshes 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 254 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-77138?
CVE-2026-77138 is a critical-severity vulnerability; its CVE record was published on August 25, 2026. The extension fails to safely process untrusted client input of an attacker-controlled cookie directly to PHP's unserialize(). A remote, unauthenticated attacker can supply a crafted serialized payload to trigger PHP Object Injection, leading to Remote Code Execution on the TYPO3 server.
When was CVE-2026-77138 made public?
CVE-2026-77138 was made public on August 25, 2026: that is the date its CVE record's CNA, TYPO3 Association, gives for when the vulnerability was made public. The CVE record itself was published on August 25, 2026. EchelonGraph's copy of the record carries a last-modified date of September 28, 2026; the record at its source may have been updated since.
Is CVE-2026-77138 actively exploited?
CVE-2026-77138 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-77138?
CVE-2026-77138 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-77138?
No fix for CVE-2026-77138 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 (TYPO3 Association) lists TYPO3 Extension "HTML5 Video Player vs. Powermail" versions up to and including 0.2.1 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-77138 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-77138?

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

Book a Demo →Browse All CVEs