# CVE-2026-85400: TYPO3 CMS - Missing Authorization in lowlevel commands

> Backend administrators can modify system configuration to escalate privileges or cause denial of service due to missing authorization checks.

- **Severity:** High 7.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 8 Sep 2026

## What is CVE-2026-85400?

CVE-2026-85400 is a high-severity missing authorization vulnerability in TYPO3 CMS, published on 8 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Backend administrators without system maintainer privileges were able to schedule any of the configuration:read, configuration:set, and configuration:show commands. This allowed them to modify arbitrary system configuration, which is normally limited to system maintainers. As a consequence, this allowed them, for example, to gain system maintainer privileges or cause a denial of service. Exploiting this vulnerability requires an administrator-level backend user account. This issue affects TYPO3 CMS versions 14.2.0-14.3.6.

Weakness: CWE-862 (Missing Authorization), CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2026-85400?


## How do I fix CVE-2026-85400?

No fix has been published for CVE-2026-85400 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-85400 being exploited?

There is no known exploitation of CVE-2026-85400 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85400 and fix it if it is affected.

What it is: CVE-2026-85400 is a high-severity missing authorization vulnerability in TYPO3 CMS, published on 8 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85400 in the wild and no public exploit code.

Affected product: TYPO3 CMS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-85400/ (Markdown: https://insights.sbomify.com/CVE-2026-85400/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85400
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85400
- OSV: https://osv.dev/vulnerability/CVE-2026-85400

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85400/
Summaries are generated and may contain mistakes; the official description above is the record.