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

> Attackers with backend access can recover sensitive data like database passwords and session cookies from the http_error_log file.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jan 2026
- **Updated:** 15 Jan 2026
- **Also known as:** GHSA-q433-j342-rp9h

## What is CVE-2026-23493?

CVE-2026-23493 is a high-severity vulnerability in Pimcore Pimcore, published on 15 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2026-23493?

4 open source packages ship an affected version, including pimcore/pimcore. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pimcore/pimcore` | Packagist | All versions | 11.5.14 |
| `pimcore/pimcore` | Packagist | All versions | 11.5.14 |
| `pimcore/pimcore` | Packagist | From 12.0.0-RC1 | 12.3.1 |
| `pimcore/pimcore` | Packagist | From 12.0.0-RC1 | 12.3.1 |

Products: Pimcore Pimcore.

## How do I fix CVE-2026-23493?

Upgrade pimcore/pimcore to a fixed version for your release line: 11.5.14 or 12.3.1.

## Is CVE-2026-23493 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-23493 exists.

## Other vulnerabilities in Pimcore Pimcore

- [CVE-2022-39365](https://insights.sbomify.com/CVE-2022-39365/): RCE vulnerability in Pimcore/Mail & Dynamic Text Layout (critical 9.8)
- [CVE-2019-18981](https://insights.sbomify.com/CVE-2019-18981/): Pimcore Access Control Issues (critical 9.8)
- [CVE-2019-18985](https://insights.sbomify.com/CVE-2019-18985/): Pimcore 2FA Vulnerable to Brute Forcing (critical 9.8)
- [CVE-2026-23492](https://insights.sbomify.com/CVE-2026-23492/): Pimcore has a Blind SQL Injection in Admin Search Find API due to an incomplete fix for CVE-2023-30848 (high 8.8)
- [CVE-2023-47637](https://insights.sbomify.com/CVE-2023-47637/): SQL Injection in Admin Grid Filter API in Pimcore (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-23493 and fix it if it is affected.

What it is: CVE-2026-23493 is a high-severity vulnerability in Pimcore Pimcore, published on 15 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-23493 exists.

Affected packages and fixed versions:
- pimcore/pimcore (Packagist): affected all versions; fixed in 11.5.14
- pimcore/pimcore (Packagist): affected all versions; fixed in 11.5.14
- pimcore/pimcore (Packagist): affected from 12.0.0-RC1; fixed in 12.3.1
- pimcore/pimcore (Packagist): affected from 12.0.0-RC1; fixed in 12.3.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-23493/ (Markdown: https://insights.sbomify.com/CVE-2026-23493/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-23493
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-23493
- OSV: https://osv.dev/vulnerability/CVE-2026-23493

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-23493/
Summaries are generated and may contain mistakes; the official description above is the record.