PatchSiren cyber security CVE debrief
CVE-2026-105116 OpenIdentityPlatform CVE debrief
OpenAM before 16.1.3 contains a latent cross-site scripting defect that places the SAML message, relay state and target URL unencoded into the load-balancer cookie bounce auto-submit page. If reachable with cookieHashRedirectEnabled set, crafted requests could execute script in the OpenAM origin, though an unrelated HTTP 500 failure prevents exploitation in released versions.
- Vendor
- OpenIdentityPlatform
- Product
- OpenAM
- CVSS
- MEDIUM 5.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-03
- Original CVE updated
- 2026-10-03
- Advisory published
- 2026-10-03
- Advisory updated
- 2026-10-03
Who should care
Defenders responsible for OpenAM deployments should assess exposure and review configurations for cookieHashRedirectEnabled to prevent potential script execution. This includes verifying affected versions and configurations, and ensuring appropriate security measures are in place to mitigate potential risks associated with this vulnerability.
Why it matters
Defenders should prioritize verification of affected OpenAM versions and review configurations for cookieHashRedirectEnabled to prevent potential script execution.
- Potential script execution in OpenAM origin
- Verification of affected versions and configurations required
- Review of cookieHashRedirectEnabled settings necessary
Technical summary
OpenAM before 16.1.3 contains a latent cross-site scripting defect that places the SAML message, relay state and target URL unencoded into the load-balancer cookie bounce auto-submit page. If reachable with cookieHashRedirectEnabled set, crafted requests could execute script in the OpenAM origin, though an unrelated HTTP 500 failure prevents exploitation in released versions. This vulnerability could allow attackers to execute script in the OpenAM origin if certain conditions are met, emphasizing the need for configuration review.
Defensive priority
Defenders should prioritize verification of affected versions and review configurations for cookieHashRedirectEnabled.
Recommended defensive actions
- Verify OpenAM version and configuration
- Review and adjust cookieHashRedirectEnabled settings
- Monitor for potential exploitation attempts
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
Evidence notes
The CVE record and NVD entry provide details on the vulnerability. Evidence of exploitation is not provided. OpenAM deployments should verify configurations and review potential exposure. Defenders should assess affected versions and configurations for cookieHashRedirectEnabled. The vulnerability places SAML message, relay state, and target URL unencoded into the load-balancer cookie bounce auto-submit page.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-105116 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-105116
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-105116 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-105116
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-v796-mg6j-9c5m
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/openam-before-16.1.3-latent-xss-in-saml-load-balancer-cookie-bounce-page
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.