Vulnerabilities in pkg:pypi/edx-enterprise

PACKAGE
Advisory Identifier: GHSA-64cv-vxpr-j6vc
Advisory Summary

CVE-2026-42860 is a HIGH (CVSS 8.5) edx-enterprise has ssrf vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting Edx enterprise libraries in the PyPI ecosystem. The issue involves edx-enterprise has ssrf via saml metadata url in sync_provider_data endpoint. Remediation is available by upgrading affected packages to version 7.0.5.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:pypi/edx-enterprise

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:pypi/edx-enterprise. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-64cv-vxpr-j6vc CVE-2026-42860 HIGH edx-enterprise has SSRF via SAML metadata URL in sync_provider_data endpoint

CVE-2026-42860 at a Glance

CVE Identifier CVE-2026-42860
GHSA Identifier GHSA-64cv-vxpr-j6vc
Severity HIGH
CVSS v3.1 Base Score 8.5
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product Edx enterprise
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 8.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-42860

To remediate this vulnerability, upgrade all affected Edx enterprise dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

edx-enterprise fixed: 7.0.5
pip install edx-enterprise>=7.0.5
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show edx-enterprise

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-42860, inspect your installed packages using pip:

pip show edx-enterprise

Analyze the terminal output to locate any version of Edx enterprise in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 7.0.5), your application is affected.

Note: The pip show edx-enterprise command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In Edx enterprise, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary The `sync_provider_data` endpoint in `SAMLProviderDataViewSet` fetches SAML metadata from a URL stored in `SAMLProviderConfig.metadata_source`. An authenticated user with the Enterprise Admin role can set this field to an arbitrary URL via the `SAMLProviderConfigViewSet` PATCH endpoint, then trigger a server-side HTTP request by calling `sync_provider_data`. The fetch in `fetch_metadata_xml()` passes the URL directly to `requests.get()` with no scheme enforcement, IP filtering, or timeout. This vulnerability was introduced when the SAML admin viewsets were migrated from `openedx-platform` into `edx-enterprise`. A related fix for the equivalent fetch path in `openedx-platform` (the `fetch_saml_metadata` Celery task) was applied in [GHSA-328g-7h4g-r2m9](https://github.com/openedx/openedx-platform/security/advisories/GHSA-328g-7h4g-r2m9). ## Details **Vulnerable code path:** `enterprise/api/v1/views/saml_utils.py`: ```python def fetch_metadata_xml(url): log.info("Fetching %s", url) if not url.lower().startswith('https'): log.warning("This SAML metadata URL is not secure! (%s)", url) response = requests.get(url, verify=True) # No IP/scheme validation response.raise_for_status() ``` `enterprise/api/v1/views/saml_provider_data.py`: ```python @action(detail=False, methods=['post'], url_path='sync_provider_data') def sync_provider_data(self, request): ... metadata_url = saml_provider.metadata_source # set via SAMLProviderConfig PATCH xml = fetch_metadata_xml(metadata_url) # triggers the fetch ``` **Missing protections:** - No HTTPS enforcement (HTTP is allowed; the warning is not enforced) - No blocking of loopback (`127.0.0.0/8`) or link-local (`169.254.0.0/16`) ranges - No blocking of RFC 1918 private ranges - No request timeout ## Proof of Concept **Prerequisites:** Authenticated user with `Enterprise Admin` role for any enterprise customer with a configured SAML Identity Provider. **Step 1:** Set a malicious metadata URL via the provider config endpoint: ```bash curl -X PATCH 'https://<instance>/auth/saml/v0/provider_config/<pk>/' \ -H 'Authorization: Bearer <JWT>' \ -H 'Content-Type: application/json' \ -d '{"metadata_source": "http://169.254.169.254/latest/meta-data/iam/security-credentials/"}' ``` **Step 2:** Trigger the server-side fetch: ```bash curl -X POST 'https://<instance>/auth/saml/v0/provider_data/sync_provider_data' \ -H 'Authorization: Bearer <JWT>' \ -H 'Content-Type: application/json' \ -d '{"enterprise_customer_uuid": "<uuid>"}' ``` The server fetches the AWS metadata endpoint. Even though XML parsing will fail, the HTTP request is made and timing/error differences confirm reachability of internal addresses. ## Impact An Enterprise Admin can use this SSRF to: - **Steal cloud credentials:** Access AWS/GCP/Azure instance metadata services to retrieve IAM temporary credentials, potentially enabling full cloud infrastructure compromise. - **Scan internal networks:** Probe internal hosts, ports, and services behind the deployment's firewall. - **Access internal APIs:** Reach databases, admin panels, or microservices not exposed to the internet. Enterprise Admin is a delegated role typically granted to corporate training managers, not platform operators. It should not grant the ability to make the server issue arbitrary outbound HTTP requests. ## Patches / Mitigations Call `validate_saml_metadata_url()` (importable from `common.djangoapps.third_party_auth.utils` as of the openedx-platform fix in [GHSA-328g-7h4g-r2m9](https://github.com/openedx/openedx-platform/security/advisories/GHSA-328g-7h4g-r2m9)) in `fetch_metadata_xml()` before calling `requests.get()`. A request timeout should also be added. Operators should additionally enforce network-level egress filtering to block outbound connections from the Open edX server to `169.254.0.0/16` and RFC 1918 ranges as a complementary control, particularly to cover hostname-based URLs that cannot be validated at the application layer.

CVE-2026-42860 Affected Edx enterprise Versions

1 component(s)
Fixed Versions:
7.0.5
Product / Package Ecosystem Affected Versions Fixed Version
edx-enterprise
PyPI
≥ 7.0.2
< 7.0.5
7.0.5

References

Frequently Asked Questions

What is CVE-2026-42860?
CVE-2026-42860 is a security vulnerability in Edx enterprise involving edx-enterprise has SSRF via SAML metadata URL in sync_provider_data endpoint under CWE-918: Server-Side Request Forgery (SSRF).
Which Edx enterprise versions are affected?
Affected versions include releases prior to 7.0.5 across affected packages: edx-enterprise.
What version fixes CVE-2026-42860?
Upgrading to 7.0.5 (or the latest patched release for your respective branch) resolves the vulnerability.
Is edx-enterprise affected?
Yes, edx-enterprise is affected in releases prior to 7.0.5. Upgrade your dependency to 7.0.5 or later.
What is the CVSS score of CVE-2026-42860?
CVE-2026-42860 has a CVSS v3.1 base score of 8.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N.
What CWE is associated with CVE-2026-42860?
CVE-2026-42860 is classified under CWE-918: Server-Side Request Forgery (SSRF) (The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.).
How can I check PyPI dependencies for CVE-2026-42860?
Run the dependency tree command: 'pip show edx-enterprise'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-64cv-vxpr-j6vc",
  "modified" : "2026-06-06T00:27:25Z",
  "published" : "2026-05-05T17:51:50Z",
  "aliases" : [ "CVE-2026-42860" ],
  "summary" : "edx-enterprise has SSRF via SAML metadata URL in sync_provider_data endpoint",
  "details" : "## Summary\n\nThe `sync_provider_data` endpoint in `SAMLProviderDataViewSet` fetches SAML metadata from a URL stored in `SAMLProviderConfig.metadata_source`. An authenticated user with the Enterprise Admin role can set this field to an arbitrary URL via the `SAMLProviderConfigViewSet` PATCH endpoint, then trigger a server-side HTTP request by calling `sync_provider_data`. The fetch in `fetch_metadata_xml()` passes the URL directly to `requests.get()` with no scheme enforcement, IP filtering, or timeout.\n\nThis vulnerability was introduced when the SAML admin viewsets were migrated from `openedx-platform` into `edx-enterprise`. A related fix for the equivalent fetch path in `openedx-platform` (the `fetch_saml_metadata` Celery task) was applied in [GHSA-328g-7h4g-r2m9](https://github.com/openedx/openedx-platform/security/advisories/GHSA-328g-7h4g-r2m9).\n\n## Details\n\n**Vulnerable code path:**\n\n`enterprise/api/v1/views/saml_utils.py`:\n```python\ndef fetch_metadata_xml(url):\n    log.info(\"Fetching %s\", url)\n    if not url.lower().startswith('https'):\n        log.warning(\"This SAML metadata URL is not secure! (%s)\", url)\n    response = requests.get(url, verify=True)  # No IP/scheme validation\n    response.raise_for_status()\n```\n\n`enterprise/api/v1/views/saml_provider_data.py`:\n```python\n@action(detail=False, methods=['post'], url_path='sync_provider_data')\ndef sync_provider_data(self, request):\n    ...\n    metadata_url = saml_provider.metadata_source  # set via SAMLProviderConfig PATCH\n    xml = fetch_metadata_xml(metadata_url)        # triggers the fetch\n```\n\n**Missing protections:**\n- No HTTPS enforcement (HTTP is allowed; the warning is not enforced)\n- No blocking of loopback (`127.0.0.0/8`) or link-local (`169.254.0.0/16`) ranges\n- No blocking of RFC 1918 private ranges\n- No request timeout\n\n## Proof of Concept\n\n**Prerequisites:** Authenticated user with `Enterprise Admin` role for any enterprise customer with a configured SAML Identity Provider.\n\n**Step 1:** Set a malicious metadata URL via the provider config endpoint:\n```bash\ncurl -X PATCH 'https://<instance>/auth/saml/v0/provider_config/<pk>/' \\\n  -H 'Authorization: Bearer <JWT>' \\\n  -H 'Content-Type: application/json' \\\n  -d '{\"metadata_source\": \"http://169.254.169.254/latest/meta-data/iam/security-credentials/\"}'\n```\n\n**Step 2:** Trigger the server-side fetch:\n```bash\ncurl -X POST 'https://<instance>/auth/saml/v0/provider_data/sync_provider_data' \\\n  -H 'Authorization: Bearer <JWT>' \\\n  -H 'Content-Type: application/json' \\\n  -d '{\"enterprise_customer_uuid\": \"<uuid>\"}'\n```\n\nThe server fetches the AWS metadata endpoint. Even though XML parsing will fail, the HTTP request is made and timing/error differences confirm reachability of internal addresses.\n\n## Impact\n\nAn Enterprise Admin can use this SSRF to:\n\n- **Steal cloud credentials:** Access AWS/GCP/Azure instance metadata services to retrieve IAM temporary credentials, potentially enabling full cloud infrastructure compromise.\n- **Scan internal networks:** Probe internal hosts, ports, and services behind the deployment's firewall.\n- **Access internal APIs:** Reach databases, admin panels, or microservices not exposed to the internet.\n\nEnterprise Admin is a delegated role typically granted to corporate training managers, not platform operators. It should not grant the ability to make the server issue arbitrary outbound HTTP requests.\n\n## Patches / Mitigations\n\nCall `validate_saml_metadata_url()` (importable from `common.djangoapps.third_party_auth.utils` as of the openedx-platform fix in [GHSA-328g-7h4g-r2m9](https://github.com/openedx/openedx-platform/security/advisories/GHSA-328g-7h4g-r2m9)) in `fetch_metadata_xml()` before calling `requests.get()`. A request timeout should also be added.\n\nOperators should additionally enforce network-level egress filtering to block outbound connections from the Open edX server to `169.254.0.0/16` and RFC 1918 ranges as a complementary control, particularly to cover hostname-based URLs that cannot be validated at the application layer.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "edx-enterprise"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "7.0.2"
      }, {
        "fixed" : "7.0.5"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 7.0.4"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/openedx/edx-enterprise/security/advisories/GHSA-64cv-vxpr-j6vc"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-42860"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/openedx/edx-enterprise"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pypa/advisory-database/tree/main/vulns/edx-enterprise/PYSEC-2026-58.yaml"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-05T17:51:50Z",
    "nvd_published_at" : "2026-05-11T18:16:36Z"
  }
}