High

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

  • Disclosed: 02.07.2026
  • Updated: 11.10.2026 10:22

Summary

SimpleSAMLphp's SAML SP ACS path does not enforce the IdP selected for an SP-initiated login. If a saved SP state contains ExpectedIssuer = IdP A, but the ACS receives a valid response from IdP B, the code logs a warning and continues processing instead of rejecting the response.

That behavior becomes security-relevant when combined with the response-processing rule that accepts an unsigned samlp:Response/@InResponseTo outside the signed assertion whenever the signed assertion's SubjectConfirmationData does not carry its own InResponseTo. A response issued by one trusted IdP can therefore be bound to SP state created for another IdP.

Impact

In a multi-IdP deployment, a lower-trust IdP can satisfy SP state created for a different expected IdP. This can bypass an SP flow that intentionally routes the user to a specific IdP, including deployments that set enable_unsolicited to false to prevent IdP-initiated logins.

The impact is highest when the SP trusts multiple IdPs with different assurance levels, tenant boundaries, or attribute namespaces, and application authorization depends on the selected/expected IdP. In those deployments this is an authentication/authorization bypass candidate. Impact strongly depends on whether an attacker can obtain a signed IdP-initiated assertion from a lower-trust trusted IdP and whether the downstream application maps identifiers globally.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package simplesamlphp/simplesamlphp >= 2.5.0, < 2.5.2, < 2.4.7 2.5.2, 2.4.7

References

CVSS score 7.1/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
Weakness (CWE)
CWE-345
Platform
Composer
Package
simplesamlphp/simplesamlphp
Disclosed
02.07.2026
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-q8r6-xj3f-wrrm - CC BY 4.0

Vulnerability history: simplesamlphp/simplesamlphp

All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (23) in the archive
Total entries
23
First → latest
01.2020 07.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • Critical 3
  • High 4
  • Medium 12
  • Low 4

Disclosures per year

  1. 2020: 6
  2. 2021: 0
  3. 2022: 12
  4. 2023: 0
  5. 2024: 4
  6. 2025: 0
  7. 2026: 1
Severity:
  1. SimpleSAMLphp SP accepts a response from an unexpected IdP when unsigned `Response/InResponseTo` is combined with a signed assertion lacking `SubjectConfirmationData/InResponseTo` this entry
    High · 7.1 CVE-2026-49284 >= 2.5.0, < 2.5.2, < 2.4.7 2.5.2, 2.4.7
  2. Critical · 9.8 CVE-2017-12868 >= 1.14.12, < 1.14.14 1.14.14
  3. High · 7.5 CVE-2017-12869 < 1.14.14 1.14.14
  4. High · 8.1 CVE-2017-18122 < 1.14.17 1.14.17
  5. Critical · 9.8 CVE-2018-6521 < 1.15.2 1.15.2
  6. High · 7.5 CVE-2011-4625 < 1.8.1 1.8.1
  7. Critical · 9.8 CVE-2017-12873 >= 1.7.0, < 1.14.11 1.14.11

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.