← Back
CVE-2026-42860
high
CVSS 8.5
SSRF (Server-Side Request Forgery) in edx-enterprise (CVE-2026-42860)
Summary
SSRF in edx-enterprise (CVE-2026-42860). Confidential information can be exposed externally. Exploitable via ``sync_provider_data``. Mitigation: upgrade to `7.0.5` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-42860** has been found in edx-enterprise.
Attackers can target a specific entry point like ``sync_provider_data`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.5/10.
What to do: upgrade edx-enterprise to **7.0.5** or later.
If unsure, ask your IT team or search "edx-enterprise CVE-2026-42860" on the vendor's site.
CVE-2026-42860 (edx-enterprise) — CWE-918 / CVSS v3 8.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `sync_provider_data` / `SAMLProviderDataViewSet` / `SAMLProviderConfig.metadata_source` / `SAMLProviderConfigViewSet`
Patched: `7.0.5` — 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
**SSRF** (CWE-918) exists in edx-enterprise. Attackers reach the vulnerable code path via ``sync_provider_data`` without authentication.
📍 Affected scope
edx-enterprise — . Attack surface: `sync_provider_data` / `SAMLProviderDataViewSet` / `SAMLProviderConfig.metadata_source` / `SAMLProviderConfigViewSet`.
🔥 Severity
Severity: High (CVSS 8.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **7.0.5**.
🛡️ 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 'edx-enterprise' .` 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 'edx-enterprise' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `edx-enterprise` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade edx-enterprise to 7.0.5ステージング環境で 7.0.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
edx-enterprise
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.5"}]}]
PyPI
edx-enterprise
[{"type":"ECOSYSTEM","events":[{"introduced":"7.0.2"},{"fixed":"7.0.5"}]}]