Quick answers
- Is CVE-2026-87953 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-87953 being exploited in the wild.
- How severe is CVE-2026-87953?
- Informational severity, published 22 October 2026.
- Which products and versions are affected?
- Miniorange Saml before 3.2.0; Packagist:Https://Packages.Drupal.Org/8 Drupal/Miniorange Saml ECOSYSTEM:introduced=0,fixed=3.2.0.
- Is there a fix for CVE-2026-87953?
- Yes. Packagist:Https://Packages.Drupal.Org/8 Drupal/Miniorange Saml: upgrade to 3.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-87953 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-87953?
- Check whether you run Miniorange Saml or Packagist:Https://Packages.Drupal.Org/8 Drupal/Miniorange Saml at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Packagist:Https://Packages.Drupal.Org/8 Drupal/Miniorange Saml: upgrade to 3.2.0 or later
Technical details
The module fails to sufficiently validate URLs parsed from identity provider metadata, leading to a server-side request forgery (SSRF) vulnerability. An authenticated attacker with permission to configure identity provider metadata can inject malicious URLs that cause the Drupal application to make requests to internal network resources or unintended external destinations. The vulnerability is mitigated by requiring administrative privileges to configure the metadata.
Affected products
- miniorange miniorange_saml before 3.2.0
Identifiers
- CVE-2026-87953
- DRUPAL-CONTRIB-2026-151
Timeline
- 2026-09-09: disclosed: Advisory published
- 2026-09-09: patched: Fix released in version 3.2.0