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.
CVE-2026-49284
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 86% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity71% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 4.9%
- KEV
- Not listed
Published
July 2, 2026
Last Modified
July 23, 2026
Advisory Details (3)
Auto-updated Jul 17, 2026SimpleSAMLphp v2.5.2
Patch available: simplesamlphp/simplesamlphp v2.5.2
https://github.com/simplesamlphp/simplesamlphp/releases/tag/v2.5.2SimpleSAMLphp v2.4.7
Patch available: simplesamlphp/simplesamlphp v2.4.7
https://github.com/simplesamlphp/simplesamlphp/releases/tag/v2.4.7SimpleSAMLphp SP accepts a response from an unexpected IdP when unsigned `Response/InResponseTo` is combined with a signed assertion lacking `SubjectConfirmationData/InResponseTo` · Advisory · simplesamlphp/simplesamlphp · GitHub
https://github.com/simplesamlphp/simplesamlphp/security/advisories/GHSA-q8r6-xj3f-wrrmVendor Advisories for CVE-2026-49284(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Packagist(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| simplesamlphp/simplesamlphp | 1.16.0 ... v2.4.6 (134 versions) | 2.4.7 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:18 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 03:50 UTCEG score recompute
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-02 21:06 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-345
Frequently asked(5)
What is CVE-2026-49284?
When was CVE-2026-49284 disclosed?
Is CVE-2026-49284 actively exploited?
What is the CVSS score of CVE-2026-49284?
How do I remediate CVE-2026-49284?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49284
Is Your Infrastructure Affected by CVE-2026-49284?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.