Skip to content
Applications

CVE-2026-55207

8.8
High
EPSS 0.67%Patch availableJul 10, 2026

Pimcore password-reset token leak enables admin takeover and 2FA bypass.

common questions

Is CVE-2026-55207 being exploited?

Not confirmed. CVE-2026-55207 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.67% probability of exploitation in the next 30 days.

How severe is CVE-2026-55207?

CVE-2026-55207 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-55207?

Yes. A fix has been recorded for CVE-2026-55207. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-55207 affect?

CVE-2026-55207 affects Pimcore prior to 2025.4.6, Pimcore prior to 2026.1.6, Pimcore Studio API (login/token). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-55207?

Upgrade to 2025.4.6 or 2026.1.6 immediately; validate/reset resetPasswordUrl as interim.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Pimcore prior to 2025.4.6Pimcore prior to 2026.1.6Pimcore Studio API (login/token)
impact

Unauthenticated attacker knowing an admin username can exfiltrate a reset token via attacker-controlled resetPasswordUrl, then authenticate as that admin and bypass 2FA.

action required

Immediate action required

affected versions
pimcore pimcore
  • affected>= 2026.1.0 and < 2026.1.6
  • affected< 2025.4.6

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free