CVE-2026-128335
What it is
Contao 4.6.0 before 5.3.54, 5.4.0-RC1 before 5.7.17, and 6.0.0-RC1 before 6.0.6 fails to invalidate existing user sessions when two-factor authentication is enabled or disabled. Because Contao\User::isEqualTo() and serialized session data omit two-factor state, attackers already holding a session keep it after the owner changes 2FA settings.
At a glance
- Exploitability
- Can be exploited over the network with a low-privilege account, but needs a user to act. Limited direct impact.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 2.1 LOW (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Weakness
- CWE-613
- Record status
- Deferred
Attack profile CVSS 4.0 · 2.1
- Attack vector
- Network
- Complexity
- High
- Attack requirements
- Present
- Privileges needed
- Low
- User interaction
- Passive
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
Raw vector
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-128335.md and follow it. Check whether this project is affected by CVE-2026-128335. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/contao/contao/commit/7618a5757347a30168139e74c7b326e3e296059d
- https://github.com/contao/contao/commit/7e7c821ce6c41c02ae85b3d9f8eff5039de3fe1e
- https://github.com/contao/contao/commit/843da308056402d94ae2dbb999959f9e2ce71fe1
- https://github.com/contao/contao/releases/tag/5.3.54
- https://github.com/contao/contao/releases/tag/5.7.17
- https://github.com/contao/contao/releases/tag/6.0.6
- https://github.com/contao/contao/security/advisories/GHSA-5mg3-mv6j-57wc
References
- https://github.com/contao/contao/blob/5.3.53/core-bundle/contao/library/Contao/User.php#L413-L446
- https://github.com/contao/contao/commit/7618a5757347a30168139e74c7b326e3e296059d
- https://github.com/contao/contao/commit/7e7c821ce6c41c02ae85b3d9f8eff5039de3fe1e
- https://github.com/contao/contao/commit/843da308056402d94ae2dbb999959f9e2ce71fe1
- https://github.com/contao/contao/releases/tag/5.3.54
- https://github.com/contao/contao/releases/tag/5.7.17
- https://github.com/contao/contao/releases/tag/6.0.6
- https://github.com/contao/contao/security/advisories/GHSA-5mg3-mv6j-57wc
- https://www.vulncheck.com/advisories/contao-before-5.3.54-5.7.17-and-6.0.6-session-invalidation-failure-on-2fa-change