CVE-2026-125163

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (45th 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-126980 (ENISA EUVD)Source: ENISA EUVD

6.3EG
EchelonGraph verdictMonitorThe upstream fix is not in a release yet: until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule, then apply it (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.3Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

The FileUpload and ImageUpload elements of the Form Framework use the property allowedMimeTypes as an allow list of MIME types accepted for upload. An empty allowedMimeTypes list was treated as "no restriction". Forms containing upload elements without any configured MIME type, for example in manually created form definitions or when all MIME types were deselected in the form editor, accepted any file except those blocked by the file deny pattern, which only covers PHP-related file extensions. This allowed unauthenticated users to upload files with browser-executable content, such as HTML or SVG documents, to the configured upload folder, which by default is located in a public storage. If attackers know the URL of an uploaded file (see TYPO3-CORE-SA-2026-029), this could lead to Cross-Site Scripting on web servers that do not apply the Content-Security-Policy recommended by TYPO3 to the form upload target folder.

CVSS
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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)
Severity63% × 45%
Impact severity (EG Severity): CVSS 6.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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: An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule, then apply it.
EPSS PROB
0.5%
EPSS %ILE
45th
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 (6.3): severity, escalated by confirmed exploitation. This CVE's 6.3 is its impact severity (EG Severity), not escalated.

EG Severity
6.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-19). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule, then apply it.

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.

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 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

November 17, 2026

Last Modified

November 17, 2026

Advisory Details (4)

Auto-updated Nov 17, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
Web page

TYPO3-CORE-SA-2026-032: Unrestricted File Upload in Form Framework - TYPO3 News

https://news.typo3.com/security/advisory/typo3-core-sa-2026-032
GitHub commit

commit ed6fdc059397 (TYPO3/typo3)

Fix landed in TYPO3/typo3 commit ed6fdc059397 — awaiting tagged release

https://github.com/TYPO3/typo3/commit/ed6fdc05939732e837e35063d02571051952c461
GitHub commit

commit c0b9519c254d (TYPO3/typo3)

Fix landed in TYPO3/typo3 commit c0b9519c254d — awaiting tagged release

https://github.com/TYPO3/typo3/commit/c0b9519c254d58ad2a7bb4db354456c2b639e293
GitHub commit

commit 6adb8d66f338 (TYPO3/typo3)

Fix landed in TYPO3/typo3 commit 6adb8d66f338 — awaiting tagged release

https://github.com/TYPO3/typo3/commit/6adb8d66f3388e88a54fc6da6922b11d03379ee2

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 16:38 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  3. 2026-11-20 05:33 UTCEchelonGraph re-scored
  4. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  5. 2026-11-18 16:33 UTCEPSS rescoreEPSS 0.5% · 46th percentile
  6. 2026-11-17 12:28 UTCEchelonGraph re-scored
  7. 2026-11-17 12:03 UTCENISA EUVD ID recordedEUVD-2026-126980 · Source: ENISA EUVD
  8. 2026-11-17 11:49 UTCEchelonGraph re-scored
  9. 2026-11-17 11:19 UTCEchelonGraph re-scoredFirst assessed: 6.3 MEDIUM
  10. 2026-11-17 11:18 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-125163?
CVE-2026-125163 is a medium-severity vulnerability; its CVE record was published on November 17, 2026. The FileUpload and ImageUpload elements of the Form Framework use the property allowedMimeTypes as an allow list of MIME types accepted for upload. An empty allowedMimeTypes list was treated as "no restriction". Forms containing upload elements without any configured MIME type, for example in…
When was CVE-2026-125163 made public?
CVE-2026-125163 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-125163 actively exploited?
CVE-2026-125163 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-125163?
CVE-2026-125163 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-125163?
An upstream fix for CVE-2026-125163 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-125163?

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