CVE-2026-49284

SimpleSAMLphp SP accepts a response from an unexpected IdP when unsigned `Response/InResponseTo` is combined with a signed assertion lacking `SubjectConfirmationData/InResponseTo`

Published Jul 17, 2026 CVSS 3.1 · 7.1 High EPSS < 1% KEV · Not listed
Description
SimpleSAMLphp versions before 1.18.6 contain an information disclosure vulnerability. Prior to 2.4.7 and 2.5.2, SimpleSAMLphp's SAML SP ACS path does not enforce the IdP selected for an SP-initiated login when unsigned Response/InResponseTo is combined with a signed assertion lacking SubjectConfirmationData/InResponseTo, allowing a response issued by one trusted IdP to be bound to SP state created for another IdP and bypass flows that route users to a specific IdP, including deployments that set enable_unsolicited to false. This issue is fixed in versions 2.4.7 and 2.5.2.

Analysis

AI-generated

Technical impact

The SimpleSAMLphp Service Provider (SP) fails to validate that an incoming SAML Response comes from the IdP that was chosen for the authentication flow. When a Response element lacks an InResponseTo attribute and the assertion also omits the SubjectConfirmationData/InResponseTo value, the SP accepts the message. The description labels this as an information disclosure vulnerability, and based on the description it is inferred that an attacker could read or manipulate authentication state or other sensitive data. The CWE-345 designation highlights the lack of proper identity verification leading to unintended information exposure.

Affected Systems

SimpleSAMLphp releases earlier than version 2.4.7, earlier than 2.5.2, and all 1.x releases before 1.18.6 are affected. These versions contain the flaw that allows a Response from an unexpected IdP to be bound to an SP session state created for another IdP.

Risk and Exploitability

The CVSS score of 7.1 signifies moderate to high severity, while the EPSS score of less than 1% indicates a low current exploitation probability, and the flaw is not listed in the CISA KEV catalog. The likely attack vector is remote: an adversary can craft a SAML Response that satisfies the signed assertion requirement and send it to the SP's Assertion Consumer Service endpoint. Based on the description it is inferred that the attacker would need either a trusted IdP capable of issuing the Response or a compromised signing key for the assertion, and that active exploitation data are not confirmed. If the SP allows unsolicited responses, the vulnerability enables unauthorized binding of the assertion to session state created for a different IdP, potentially exposing sensitive data.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to SimpleSAMLphp v2.4.7, v2.5.2, or any later release that contains the fix.
  • Configure the SP to reject unsigned Response/InResponseTo values and enforce explicit IdP checks for sessions; for deployments that set enable_unsolicited to false, verify that this setting remains enabled.
  • Limit network access to the ACS endpoint to known IdP servers only, using firewall rules or a reverse proxy to block unknown sources.

Generated by OpenCVE AI on July 30, 2026 at 23:44 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-q8r6-xj3f-wrrm SimpleSAMLphp SP accepts a response from an unexpected IdP when unsigned `Response/InResponseTo` is combined with a signed assertion lacking `SubjectConfirmationData/InResponseTo`
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Simplesamlphp
Simplesamlphp simplesamlphp
Vendors & Products Simplesamlphp
Simplesamlphp simplesamlphp
Type Values Removed Values Added
Description SimpleSAMLphp versions before 1.18.6 contain an information disclosure vulnerability. Prior to 2.4.7 and 2.5.2, SimpleSAMLphp's SAML SP ACS path does not enforce the IdP selected for an SP-initiated login when unsigned Response/InResponseTo is combined with a signed assertion lacking SubjectConfirmationData/InResponseTo, allowing a response issued by one trusted IdP to be bound to SP state created for another IdP and bypass flows that route users to a specific IdP, including deployments that set enable_unsolicited to false. This issue is fixed in versions 2.4.7 and 2.5.2.
Title SimpleSAMLphp SP accepts a response from an unexpected IdP when unsigned `Response/InResponseTo` is combined with a signed assertion lacking `SubjectConfirmationData/InResponseTo`
Weaknesses CWE-345
References
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N'}

Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 20, 2026, 7:22 PM
Reserved
May 28, 2026, 8:07 PM
Status
Analyzed
Published
Jul 17, 2026, 8:17 PM
Modified
Jul 30, 2026, 1:39 PM