Categories
CVE-2026-5343 high CVSS 7.4

Vulnerability in Drupal SAML SSO - Service Provider (CVE-2026-5343)

Summary

Vulnerability in Drupal SAML SSO - Service Provider (CVE-2026-5343). Confidential information can be exposed externally.

Original description

The description as published by the source.

This module enables you to perform SAML-protocol-based single-sign-on (SSO) on a Drupal site.

The module doesn't sufficiently block access, leading to a authentication bypass vulnerability.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-5343 has been found in Drupal SAML SSO - Service Provider.
Confidential information can be exposed externally. CVSS score: 7.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Drupal SAML SSO - Service Provider CVE-2026-5343" on the vendor's site.

CVE-2026-5343 (Drupal SAML SSO - Service Provider) — CWE-754 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
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-754) exists in Drupal SAML SSO - Service Provider.

📍 Affected scope

Check the vendor advisory for the affected versions of Drupal SAML SSO - Service Provider.

🔥 Severity

Severity: High (CVSS 7.4/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Drupal SAML SSO - Service Provider を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Packagist:https://packages.drupal.org/8 drupal/miniorange_saml
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.4"}],"database_specific":{"constraint":"<3.1.4"}}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details