- Package
- drupal/cas_server
- Fixed in
- 2.0.4, 2.1.3
- Published
- Wed 9 Sep 2026, 18:15 LisbonUpdated Sun 25 Oct 2026, 23:25 Lisbon
In plain words
The CAS Server module does not sufficiently check the service URL used to redirect a user during logout, allowing an attacker to redirect them to another site. The attacker must convince the user to click a specially crafted link. This does not directly compromise the CAS server or bypass authentication.
Am I affected?
Look for drupal/cas_server and its version in composer.lock. The advisory lists fixes in 2.0.4 and 2.1.3, but gives no affected version ranges. Check whether your project uses the module's logout redirect feature; no specific configuration or database is named as a condition.
What to do
Check which version you have, then update to a fixed release for your branch (2.0.4, 2.1.3):
composer show drupal/cas_server | grep versions
composer update drupal/cas_server
If your version constraint in composer.json keeps you below a fixed release, raise it first. Whether your configuration is affected, and the exact version ranges, are in the advisory itself.
If you cannot update yet
Exploitation requires user interaction: an attacker must convince a user to click a specially crafted link.
The advisory's description
This module enables you to turn a Drupal install into the Central Authentication System (CAS) Server. It makes your database the primary location for other systems to use for authentication in a SSO environment.
The module doesn't sufficiently check the service URL used to redirect the user during logout, leading to an open redirect.
This vulnerability is mitigated by the fact that an attacker must convince a user to click a specially crafted link. The vulnerability cannot be exploited without user interaction and does not allow an attacker to directly compromise the CAS server or bypass authentication.
The advisory
- OSV.dev: DRUPAL-CONTRIB-2026-135
- The week's digest, with the other advisories from 7 Sep 2026
- All advisories for drupal/cas_server