CVE-2026-15243
NVD: Apereo CAS Client accepts any CA-trusted certificate for any hostname, provided the URL the client is calling matches the configured allowlist or regex. NVD: 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. NVD: This can lead to intercepting the CAS exchange, capturing the Ticket-Granting Ticket (TGT), and subsequently obtaining Service Tickets on behalf of the victim.
7.4 Severity
HIGH EPSS
0.0017 (7) KEV
-
Source-published summary
NVD: Apereo CAS Client accepts any CA-trusted certificate for any hostname, provided the URL the client is calling matches the configured allowlist or regex. NVD: 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. NVD: This can lead to intercepting the CAS exchange, capturing the Ticket-Granting Ticket (TGT), and subsequently obtaining Service Tickets on behalf of the victim.
Possible impact
This high severity issue needs human triage to confirm exposure, affected versions, and vendor guidance for high severity review.
Affected context
Affected product or version requires source confirmation.
Remediation / advisory
Remediation reference present; patch status requires confirmation in the linked advisory.
Why it matters
This high severity issue needs human triage to confirm exposure, affected versions, and vendor guidance for high severity review.; CVSS 7.4 (HIGH); EPSS percentile 7; not listed in KEV; Remediation reference present; patch status requires confirmation in the linked advisory; sources: NVD, OSV.
What to verify
Confirm affected product/version, vendor advisory, patch or mitigation, and exposure.
Exposure hint
exposure unknown
Impact tags
Urgency reasons
Source-derived note
Summary derived from NVD / OSV description; unsafe procedural detail is not shown.
Redaction metadata
- source summary used
- True
- fallback summary used
- False
- unsafe procedural detail present
- false
- raw source displayed
- false
- public summary redacted
- true
Remediation handoff
Public-safe static handoff for human/Codex remediation planning. Scan, patch, external execution, and auto remediation are disabled.
Safety note
This radar shows source-published defensive context only. Exploit procedures, exploit strings, scanner commands, and auto-remediation are not provided.