← Back
CVE-2026-49289
Vulnerability in simplesamlphp/saml2 (CVE-2026-49289)
Summary
vulnerability in simplesamlphp/saml2 (CVE-2026-49289). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `4.20.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-49289** has been found in simplesamlphp/saml2.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade simplesamlphp/saml2 to **4.20.3** or later.
If unsure, ask your IT team or search "simplesamlphp/saml2 CVE-2026-49289" on the vendor's site.
CVE-2026-49289 (simplesamlphp/saml2) — CWE-400 /
Patched: `4.20.3` — 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.
❓ What is the problem
**A vulnerability** (CWE-400) exists in simplesamlphp/saml2.
📍 Affected scope
simplesamlphp/saml2 — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **4.20.3**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'simplesamlphp/saml2' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'simplesamlphp/saml2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `simplesamlphp/saml2` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade simplesamlphp/saml2 to 4.20.3ステージング環境で 4.20.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
simplesamlphp/saml2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.20.3"}]}]
composer
simplesamlphp/saml2-legacy
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.20.3"}]}]