Vulnerability in simplesamlphp/simplesamlphp (CVE-2026-49284)
Summary
Vulnerability in simplesamlphp/simplesamlphp (CVE-2026-49284). Data can be tampered with by attackers. Exploitable via SubjectConfirmationData. Mitigation: upgrade to 2.4.7 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-49284 has been found in simplesamlphp/simplesamlphp.
Attackers can target a specific entry point like SubjectConfirmationData over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: upgrade simplesamlphp/simplesamlphp to 2.4.7 or later.
If unsure, ask your IT team or search "simplesamlphp/simplesamlphp CVE-2026-49284" on the vendor's site.
CVE-2026-49284 (simplesamlphp/simplesamlphp) — CWE-345 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: SubjectConfirmationData / InResponseTo / enable_unsolicited / false
Patched: 2.4.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-345) exists in simplesamlphp/simplesamlphp. Attackers reach the vulnerable code path via SubjectConfirmationData.
Check the vendor advisory for the affected versions of simplesamlphp/simplesamlphp. Attack surface: SubjectConfirmationData / InResponseTo / enable_unsolicited / false.
Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.
Update to 2.4.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'simplesamlphp/simplesamlphp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'simplesamlphp/simplesamlphp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
simplesamlphp/simplesamlphpを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade simplesamlphp/simplesamlphp to 2.4.7ステージング環境で 2.4.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-49284 simplesamlphp
- Ubuntu UBUNTU-CVE-2026-49284 simplesamlphp
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com