pimcore/pimcore security advisory

CVE-2026-23493: Pimcore ENV Variables and Cookie Informations are exposed in http_error_log

CVE-2026-23493 is a high-severity information disclosure vulnerability in the PHP package pimcore/pimcore (CVSS 4.9), published 15 January 2026. The advisory does not name a fixed version. Exploiting it needs an admin-level account.

high 4.9 published 2026-01-15 · updated 2026-06-17

Affected versions: <= 11.5.13
>= 12.0.0-RC1, <= 12.3
Fixed in: not stated
Newest release: 2026.3.4
Severity: High · CVSS 4.9
Type: Information disclosure
CWE-532
Exploited in the wild: Not on the CISA KEV list
checked 2026-11-04

Is your pimcore/pimcore version affected?

Run composer show pimcore/pimcore in your project, then enter the version. We check it against this and every other known pimcore/pimcore advisory.

Who can exploit CVE-2026-23493

Access: A high-privilege account in the app, such as an admin.

CVSS vector (scored by NVD): CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Your app is only exposed if it uses the affected part of pimcore/pimcore. The advisory below says which part that is. If you are not sure, upgrade anyway: it costs less than finding out.

How to fix CVE-2026-23493 in pimcore/pimcore

Find the installed version: composer show pimcore/pimcore. If you never required it yourself, composer why pimcore/pimcore shows which package pulls it in.
Update it: composer update pimcore/pimcore --with-all-dependencies.
If Composer will not go that high, your composer.json constraint is holding it back. Widen it (for example "pimcore/pimcore": "^2026.3.4" if you can take that version), or upgrade the package that requires it.
Run composer audit. It reads the same advisory data and should no longer list CVE-2026-23493.
Commit composer.lock and deploy it. On the server, run composer install --no-dev from the lock file, not composer update.

If you cannot upgrade yet

General hardening for information disclosure issues while the upgrade waits. None of it replaces the fix.

Make sure APP_DEBUG (or your framework's debug mode) is off in production and error pages show no stack traces.
If your app does not use the affected feature, note that in your audit, but still plan the upgrade.

The CVE-2026-23493 advisory

Pimcore is an Open Source Data & Experience Management Platform. Prior to 12.3.1 and 11.5.14, the http_error_log file stores the $_COOKIE and $_SERVER variables, which means sensitive information such as database passwords, cookie session data, and other details can be accessed or recovered through the Pimcore backend. This vulnerability is fixed in 12.3.1 and 11.5.14.

Description from the CVE record, published by GitHub (the CVE Numbering Authority), via the NVD entry for CVE-2026-23493. Advisory title: “Pimcore ENV Variables and Cookie Informations are exposed in http_error_log”.

References

GitHub advisory GHSA-q433-j342-rp9h github.com
Fix commit 002ec7d github.com
Pull request #18918 github.com
Release v11.5.14 github.com
Release v12.3.1 github.com

Other pimcore/pimcore advisories

Need help patching or upgrading? Laskyr does PHP and Laravel security fixes and upgrades. Tell us what you run and we reply with a plan and a price.

Ask about a fix

Where this data comes from

Affected and fixed versions: the Packagist security advisories API (GitHub Advisory Database and FriendsOfPHP), the same data composer audit uses. Synced 2026-11-03.
Description, score, weakness and references: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Exploited-in-the-wild status: the CISA Known Exploited Vulnerabilities catalog, checked 2026-11-04.
Compiled by Daniel Lasek at Laskyr from the sources above. The summary, “who can exploit it”, “how to fix it” and hardening sections are our plain-English reading of the record and are generated from it. The quoted description is the record's own text. Spot an error? Tell us.