Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3amended

Contao: Path traversal in the images controller

CVE-2026-107844GHSA-mrvp-7wmx-5m4h

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (contao/core-bundle 5.7.12, 5.3.50), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist contao/core-bundle

    Affected
    >= 4.1.0, < 5.3.50>= 5.4.0-RC1, < 5.7.12
    Fixed in
    5.7.12, 5.3.50

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2026-107844: 0.31% estimated exploitation activity in the next 30 days; percentile 24.17 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

ImagesController joins the user controlled {path} onto the configured image target directory with Path::join(), which canonicalises .. segments, and never calls Path::isBasePath() to confirm the result stayed inside that directory. An unauthenticated GET with percent encoded dot segments therefore escapes the directory and the file is returned by BinaryFileResponse. Reads are bounded to the extensions in contao.image.validextensions, and paths below the upload directory fail for an unrelated reason, so this is reported as a missing boundary check rather than as a general arbitrary file read. Both Apache with the shipped public/.htaccess and nginx with the documented configuration are affected. Impact Any unauthenticated visitor can read files that are deliberately kept outside the document root, anywhere under the project directory, as long as the name ends in one of contao.image.validextensions (jpg, jpeg, gif, png, tif, tiff, bmp, svg, svgz, webp). The route also acts as an…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-mrvp-7wmx-5m4h

  2. Revision 1 · created ·

    Published from osv record GHSA-mrvp-7wmx-5m4h

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-107844

Advisory: Contao: Path traversal in the images controller
IDs: CVE-2026-107844, GHSA-mrvp-7wmx-5m4h
Record: https://patchnext.com/advisories/cve-2026-107844 (revision 2, source checked 26 Oct 2026, 14:53 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: contao/core-bundle 5.7.12, 5.3.50. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist contao/core-bundle: affected >= 4.1.0, < 5.3.50; >= 5.4.0-RC1, < 5.7.12; fixed in 5.7.12, 5.3.50

## Suggested inspection (read-only)
- Packagist contao/core-bundle: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on contao/core-bundle.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-mrvp-7wmx-5m4h (OSV record GHSA-mrvp-7wmx-5m4h lists affected ranges: Packagist contao/core-bundle >=4.1.0 =5.4.0-RC1 <5.7.12 (fixed))
- Verified: https://github.com/advisories/GHSA-mrvp-7wmx-5m4h (GitHub-reviewed advisory GHSA-mrvp-7wmx-5m4h lists affected ranges: Packagist contao/core-bundle >=4.1.0 =5.4.0-RC1 <5.7.12)

Commands are suggestions: review each one before running it.

Loading voting…