{"answers":{"affected":"2 open source packages ship an affected version, including org.keycloak:keycloak-services.","exploited":"There is no known exploitation of CVE-2026-1190 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-1190 is a low-severity vulnerability in Red Hat JBoss Enterprise Application Platform 8, published on 26 Jan 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-1190 and fix it if it is affected.\n\nWhat it is: CVE-2026-1190 is a low-severity vulnerability in Red Hat JBoss Enterprise Application Platform 8, published on 26 Jan 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-1190 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.keycloak:keycloak-services (Maven): affected all versions up to 26.5.2; no fix listed\n- org.keycloak:keycloak-services (Maven): affected all versions up to 26.5.2; no fix listed\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-1190/ (Markdown: https://insights.sbomify.com/CVE-2026-1190/index.md)","id":"CVE-2026-1190","markdown":"https://insights.sbomify.com/CVE-2026-1190/index.md","name":"CVE-2026-1190","record":{"aliases":["GHSA-63v5-26vq-m4vm","MINI-7c8j-37gv-5342","MINI-94v9-hj8h-68rf"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Keycloak SAML brokering","requires_auth":"none","summary":"Attackers can extend SAML response validity by bypassing NotOnOrAfter checks, causing resource consumption or unexpected session durations in Keycloak SAML brokering.","user_interaction":"required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-112","name":"Missing XML Validation"}],"description":"A flaw was found in Keycloak's SAML brokering functionality. When Keycloak is configured as a client in a Security Assertion Markup Language (SAML) setup, it fails to validate the `NotOnOrAfter` timestamp within the `SubjectConfirmationData`. This allows an attacker to delay the expiration of SAML responses, potentially extending the time a response is considered valid and leading to unexpected session durations or resource consumption.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Keycloak's missing timestamp validation allows attackers to extend SAML response validity periods","id":"CVE-2026-1190","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"JavaScript Notifier \u003c= 1.2.8 - Authenticated (Administrator+) Stored Cross-Site Scripting via Plugin Settings","id":"CVE-2026-1191"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["26.5.2"],"package":"org.keycloak:keycloak-services","purl":null,"source":"GHSA-63v5-26vq-m4vm"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["26.5.2"],"package":"org.keycloak:keycloak-services","purl":"pkg:maven/org.keycloak/keycloak-services","source":"GHSA-63v5-26vq-m4vm"}],"prev":{"headline":"Cross-site scripting in LeadBI Plugin for WordPress","id":"CVE-2026-1189"},"products":["Red Hat JBoss Enterprise Application Platform 8","Red Hat JBoss Enterprise Application Platform Expansion Pack","Red Hat Single Sign-On 7","Red Hat build of Keycloak 26.4","Red Hat build of Keycloak 26.4.10"],"published":"2026-01-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-03-06","vendors":["Red Hat"]},"summary":"Attackers can extend SAML response validity by bypassing NotOnOrAfter checks, causing resource consumption or unexpected session durations in Keycloak SAML brokering.","url":"https://insights.sbomify.com/CVE-2026-1190/"}