Quick answers
- Is CVE-2026-87947 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-87947 being exploited in the wild.
- How severe is CVE-2026-87947?
- Informational severity, published 22 October 2026.
- Which products and versions are affected?
- miniOrange SAML SSO - Service Provider 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-87947?
- 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-87947 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-87947?
- Check whether you run miniOrange SAML SSO - Service Provider 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 enforce a fixed signature algorithm for SAML assertion validation, instead allowing the algorithm to be specified in the incoming SAML response. This enables signature algorithm substitution attacks where an attacker crafts a response using a weaker or different algorithm than the IdP's configured key type expects. An attacker capable of submitting a malicious SAML response can exploit this to forge or replay assertions and achieve authentication bypass. The vulnerability is fixed in version 3.2.0.
Affected products
- miniorange SAML SSO - Service Provider before 3.2.0
Identifiers
- CVE-2026-87947
- DRUPAL-CONTRIB-2026-145
Timeline
- 2026-09-09: disclosed