CVE-2026-119623

CRITICALPre-NVD 9.49.4
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (53rd 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

Also known asEUVD-2026-126975 (ENISA EUVD)Source: ENISA EUVD

9.4EG
EchelonGraph verdictPlan mitigationNo release containing the referenced fix is confirmed: check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.4Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

The installer (first installation wizard) could be re-enabled on an already configured instance by placing a file whose name starts with FIRST_INSTALL in the public web root or the project root. The installer then became accessible without authentication, allowing for example to change the database connection and to create a new administrator and system maintainer account, which leads to remote code execution. As demonstrated in TYPO3-CORE-SA-2026-026, such a file could be created by an authenticated, low-privileged backend user without any further permissions. Other ways of creating files in the web root, as well as leftover or restored marker files, could be abused in the same way.

With the fixed versions, the installer can no longer be re-enabled on an already configured instance by a marker file. A new internal setting $GLOBALS['TYPO3_CONF_VARS']['SYS']['isInstalling'] is stored in the system configuration and is only enabled while a new installation is running. Additionally, only the exact file names FIRST_INSTALL and FIRST_INSTALL.txt are accepted as marker files.

CVSS
9.4
EG Score
9.4CRITICALmedium confidence
EG Risk
43
EG Risk 43/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)
Severity94% × 45%
Impact severity (EG Severity): CVSS 9.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 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 referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.
EPSS PROB
0.7%
EPSS %ILE
53rd
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.4): severity, escalated by confirmed exploitation. This CVE's 9.4 is its impact severity (EG Severity), not escalated.

EG Severity
9.4 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). 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.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.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 referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.

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.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

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

November 17, 2026

Last Modified

November 17, 2026

Advisory Details (1)

Auto-updated Nov 17, 2026
Fix referenced — no release confirmed yet.
Web page

TYPO3-CORE-SA-2026-027: Missing Authentication in Installer - TYPO3 News

https://news.typo3.com/security/advisory/typo3-core-sa-2026-027

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 6× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 21:17 UTCEchelonGraph re-scored
  2. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  3. 2026-11-20 22:19 UTCEchelonGraph re-scored
  4. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  5. 2026-11-19 23:14 UTCEchelonGraph re-scored
  6. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  7. 2026-11-19 10:30 UTCEchelonGraph re-scored
  8. 2026-11-18 16:33 UTCEPSS rescoreEPSS 0.9% · 61st percentile
  9. 2026-11-17 12:28 UTCEchelonGraph re-scored
  10. 2026-11-17 12:03 UTCENISA EUVD ID recordedEUVD-2026-126975 · Source: ENISA EUVD
  11. 2026-11-17 11:49 UTCEchelonGraph re-scored
  12. 2026-11-17 11:19 UTCEchelonGraph re-scoredFirst assessed: 9.4 CRITICAL
  13. 2026-11-17 11:18 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-119623?
CVE-2026-119623 is a critical-severity vulnerability; its CVE record was published on November 17, 2026. The installer (first installation wizard) could be re-enabled on an already configured instance by placing a file whose name starts with FIRST_INSTALL in the public web root or the project root. The installer then became accessible without authentication, allowing for example to change the database…
When was CVE-2026-119623 made public?
CVE-2026-119623 was made public on November 17, 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 November 17, 2026. EchelonGraph's copy of the record carries a last-modified date of November 17, 2026; the record at its source may have been updated since.
Is CVE-2026-119623 actively exploited?
CVE-2026-119623 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-119623?
CVE-2026-119623 has a CVSS base score of 9.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-119623?
A fix for CVE-2026-119623 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-119623?

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