Issue Bug Closed

#110049Serialized scheduler database tasks are blocked by DenyListSerializer because of references to TYPO3\CMS\Core\Log\Logger

Benjamin Franzke 06/11/26, 11:40 updated 08/11/26, 08:50

Description

Originally reported by @oliverhauser by slack: https://typo3.slack.com/archives/C03AM9R17/p1781158608125549

> Since the latest security updates, our deploy pipelines have been failing across all versions because the new DenyListSerializer finds old logger entries in the fields of the scheduler tasks, which causes an exception.
>
> The entries are difficult to fix across hundreds of stages; a simple SQL search and replace does not work, as the scheduler field is a BLOB, such as s:9:„\0*\0logger";O:25:„TYPO3\CMS\Core\Log\Logger":5
>
> Open and save old scheduler task records via the backend module will may remove the logger entries. However, if the stage has already been updated, the scheduler module triggers an exception error: "Denied class name 'TYPO3\CMS\Core\Log\Logger' found in payload".

Reviews 3

History 312

  1. Benjamin Franzke commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-06-16T06:10:11+00:00" > 06/16/26, 06:10 </span>

    Applied in changeset commit:2d2ffd6fc9b20de9f4e63f2b3b46476ff8d1a2b5.