Someone who can put a file with a particular name in your public web root or project root can reopen TYPO3's installer on a site that's already set up. The installer then works without logging in. They can change the database connection and create a new administrator and system maintainer account, which lets them run code on your server.
How it works
The TYPO3 advisory says the first-install wizard decided whether to run based on a marker file alone. Any backend user could create such a file through TYPO3-CORE-SA-2026-026, and other ways of writing files to the web root, or marker files left over or restored from a backup, work the same way. The fix adds a $GLOBALS['TYPO3_CONF_VARS']['SYS']['isInstalling'] setting, so the installer only opens while a new installation is running. It also accepts only the exact names FIRST_INSTALL and FIRST_INSTALL.txt.
After you update
TYPO3 advises checking the public web root and project root for unexpected files whose names start with FIRST_INSTALL. It also advises reviewing backend accounts with administrator or system maintainer rights for ones you don't recognize.