CVE-2026-15243
Apereo CAS Client accepts any CA-trusted certificate for any hostname, provided the URL the client is calling matches the configured allowlist or regex. An attacker with a MITM position (DNS poisoning, rogue Wi-Fi, malicious proxy, etc.) can provide any CA-signed certificate for a hostname that matches the configured allowlist or regex. This can lead to intercepting the CAS exchange, capturing the Ticket-Granting Ticket (TGT), and subsequently obtaining Service Tickets on behalf of the victim. Because maintainers contact attempts were unsuccessful, vulnerabilities have only been confirmed in version 4.1.0 (Java Apereo CAS Client) and 3.6.4 (Jasig CAS Client) but may also affect other versions.
Scoring
- Severity
- HIGH
- CVSS base score
- 7.4
- CVSS vector
- CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- EPSS probability
- 0.17%
- CWE
- CWE-297
- Published
- 2026-07-24
- Last modified
- 2026-07-24
Affected products
- Apereo Java Apereo CAS Client
- Apereo Jasig CAS Client
Weakness type
Related vulnerabilities
- CVE-2026-79636 — Dell SCG 5.0 Appliance versions prior to 5.36.00.16 and Dell SCG 5.0 Application versions prior to...
- CVE-2026-84197 — In Eclipse Ditto's Node.js JavaScript client, all released versions of...
- CVE-2026-84393 — A improper validation of certificate with host mismatch vulnerability in Fortinet FortiOS 7.6.1...
- CVE-2026-79943 — Dell SCG 5.0 Appliance versions prior to 5.36.00.16 and Dell SCG 5.0 Application versions prior to...
- CVE-2026-9744 — Vulnerabilities exists in IBM Netezza Software
- CVE-2026-62243 — Netty 4.2.0 through 4.2.16 TLS Hostname Verification Bypass
- CVE-2026-53583 — libgit2: Inverted IP SubjectAltName Comparison in OpenSSL Backend
- CVE-2026-49457 — QUIC has Broken TLS verification