{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-15243 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-15243 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-15243 is a high-severity vulnerability in Apereo Jasig CAS Client, published on 24 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-15243 and fix it if it is affected.\n\nWhat it is: CVE-2026-15243 is a high-severity vulnerability in Apereo Jasig CAS Client, published on 24 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-15243 in the wild and no public exploit code.\n\nAffected product: Apereo Jasig CAS Client. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-15243/ (Markdown: https://insights.sbomify.com/CVE-2026-15243/index.md)","id":"CVE-2026-15243","markdown":"https://insights.sbomify.com/CVE-2026-15243/index.md","name":"CVE-2026-15243","record":{"aliases":["GHSA-52jg-6vw4-42p8"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Java CAS Client","requires_auth":"none","summary":"Attackers can bypass certificate validation in Apereo CAS Client to intercept authentication tickets via Man-in-the-Middle attacks.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-297","name":"Improper Validation of Certificate with Host Mismatch"}],"description":"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. \n\nBecause 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Improper Validation of Certificate in CAS Client","id":"CVE-2026-15243","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in HUSKY","id":"CVE-2026-15244"},"packages":[],"prev":{"headline":"ChatBot for eCommerce – WoowBot \u003c 4.8.4 - Unauthenticated Gemini API Key Abuse via qcld_gemini_response","id":"CVE-2026-15241"},"products":["Jasig CAS Client","Java Apereo CAS Client"],"published":"2026-07-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-24","vendors":["Apereo"]},"summary":"Attackers can bypass certificate validation in Apereo CAS Client to intercept authentication tickets via Man-in-the-Middle attacks.","url":"https://insights.sbomify.com/CVE-2026-15243/"}