Advisory record · 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`

CVSS 7.1 HighEPSS 0.0022 · 12th percentile

Published by the GitHub Advisory Database at 2 Jul 2026, 20:47 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
simplesamlphp/simplesamlphpPackagist>=2.5.0, <2.5.2 || <2.4.72.5.2, 2.4.7
Identifiers
GHSA-q8r6-xj3f-wrrm · CVE-2026-49284 · PKSA-569h-6vqh-5xr3
Weakness (CWE)
CWE-345
Published
2 Jul 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

SimpleSAMLphp versions below 2.4.7 and from 2.5.0 up to (not including) 2.5.2 are affected. When a saved SP login state expects one identity provider but the assertion consumer service accepts a valid response from a different trusted IdP, the SP only logs a warning and continues, and an unsigned InResponseTo attribute can be accepted for that response. An attacker who controls or can obtain a signed assertion from a lower-trust trusted IdP could therefore bypass a flow meant to route users to a specific IdP, which matters most in multi-IdP deployments. Upgrade to 2.4.7 or 2.5.2.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.1 High 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0022, the 12th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:00 UTC First seen by agentprime
  2. 31 Oct 2026, 14:00 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.