GUYCOLLE GmbH

← Blog

· Contao · 3 min read

Contao security releases of 11 November 2026 at a glance

Contao patched three branches at once on 11 November 2026 and closed a stored XSS flaw in the file manager rated as critical.

Contao-Sicherheitsrunde vom 11. November 2026 im Überblick Contao

What was released on 11 November

Leo Feyer announced the round on 29 October. Delivery came on time on Wednesday morning, with 6.0.6 reaching Packagist at 07:39 UTC. All bundles carry the same version number, so core-bundle, news-bundle, newsletter-bundle, calendar-bundle and the rest are included.

The changelog for 5.3.54 lists eight entries. The most severe is a stored cross-site scripting issue in the file manager (GHSA-xh3r-77ch-frm3), rated critical. A back end account with upload or rename permission can craft a file name so that JavaScript runs during certain actions performed by other back end users. Everything from Contao 4.0.0 onwards is affected.

On top of that there is a file mount bypass in DC_Folder::editAll (CVE-2026-126662, CVSS 7.1), a path traversal via the image insert tag (CVE-2026-126663), a missing session invalidation when two-factor authentication is switched on or off (CVE-2026-128335, CVSS 2.1), XSS in the figure insert tag, an insert tag injection in the breadcrumb module on 404 pages, insufficient CSRF protection at the back end login, a header leak in the crawler and a pinning error in the HttpClient for private networks. Several advisories on contao.org still show placeholders where the CVE numbers belong. For CVE-2026-126662, no exploits were publicly known on the day of release.

The risk sits with your editorial accounts

Three of the flaws require an existing back end account. The critical XSS issue needs upload or rename permission, the file mount bypass needs file manager access, and the path traversal works with ordinary editor rights. The attack surface therefore grows with the number of back end accounts, and visitor numbers make no difference.

For agencies this is the awkward combination. Freelancers, client-side editors and image suppliers usually hold exactly these permissions. An account that has belonged to nobody for two years counts here as well.

The crawler header leak and the HttpClient issue affect installations with the crawler enabled or with internal targets on the network. Setups with staging environments or intranet hosts should check this too.

The version landscape behind it

Contao 4.13 reached end of life on 14 February 2026, with 4.13.58 as the final release. The critical XSS flaw affects these installations, and no patch exists or will be published. Anyone still running it has a migration project.

5.7 LTS is the calm choice. Active support runs until 14 February 2029, security fixes until 14 February 2030. Contao 6.0, by contrast, is maintained only until 14 February 2027, after which the move to 6.1 is due. 5.3 LTS loses active support on the same date, with security fixes continuing there until February 2028.

Contao 6 requires PHP 8.4. When upgrading from 5.3, the path runs through the current 5.7.x first, because the database migrations build on it. A contao:filesync belongs in the procedure beforehand.

What to do now

Start with an overview of every instance you look after. Version, PHP version and the number of back end accounts with file manager permission are enough as a data set. The order of work follows from that.

Installations with many external editors come first, regardless of project size. After the update, a short counter-test with a restricted account against the edit multiple action outside the permitted file mount is worth the few minutes.

A rushed migration from 5.7 to 6.0 is unnecessary because of this round, as all three branches are patched.

  • Target versions: 5.3.54, 5.7.17 or 6.0.6

  • Review file manager permissions, access to templates and configuration does not belong in an editorial account

  • Actively terminate existing sessions after two-factor changes

  • Diary entry 14.02.2027: end of active support for 5.3 LTS and end of 6.0

  • Diary entry 14.02.2028: end of security fixes for 5.3 LTS

  • Contao 4.13: plan the migration, no further patches are coming

More posts

Get in touch.

Tell us what's stuck or what you want to build. You'll reach someone who knows the answer, not a switchboard.