CVE-2026-49283: Simplesamlphp/saml2 Authentication Bypass Vulnerability

HIGH
Advisory Identifier: GHSA-6929-8p9f-26jx
CVSS 8.7
CWE-295
Published
Advisory Summary

CVE-2026-49283 is a HIGH (CVSS 8.7) authentication bypass vulnerability (CWE-295: Improper Certificate Validation) affecting Simplesamlphp/saml2 libraries in the Packagist ecosystem. The issue involves simplesamlphp http-artifact tls validator confusion allows cross-idp authentication bypass. Remediation is available by upgrading affected packages to version 6.2.1, 5.0.6, 4.20.2, 4.19.3.

CVE-2026-49283 at a Glance

CVE Identifier CVE-2026-49283
GHSA Identifier GHSA-6929-8p9f-26jx
Severity HIGH
CVSS v3.1 Base Score 8.7
CWE Classification CWE-295: Improper Certificate Validation
Affected Product Simplesamlphp/saml2
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 8.7

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

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

How to Fix CVE-2026-49283

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

simplesamlphp/saml2 fixed: 6.2.1
Upgrade simplesamlphp/saml2 to 6.2.1
simplesamlphp/saml2 fixed: 5.0.6
Upgrade simplesamlphp/saml2 to 5.0.6
simplesamlphp/saml2 fixed: 4.20.2
Upgrade simplesamlphp/saml2 to 4.20.2
simplesamlphp/saml2-legacy fixed: 4.20.2
Upgrade simplesamlphp/saml2-legacy to 4.20.2
simplesamlphp/saml2 fixed: 4.19.3
Upgrade simplesamlphp/saml2 to 4.19.3
simplesamlphp/saml2-legacy fixed: 4.19.3
Upgrade simplesamlphp/saml2-legacy to 4.19.3
Verify Direct and Transitive Dependencies

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

inspect dependencies for simplesamlphp/saml2

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-49283, inspect your project dependencies for Simplesamlphp/saml2:

inspect dependencies for simplesamlphp/saml2

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

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-295: Improper Certificate Validation, where the product does not validate, or incorrectly validates, a certificate. In Simplesamlphp/saml2, 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 SimpleSAMLphp's HTTP-Artifact receive path can treat an unsigned embedded SAML `Response` as cryptographically valid for the wrong IdP. In the `HTTPArtifact::receive()` flow, the SOAP `ArtifactResponse` receives a TLS-based validator from `SOAPClient::addSSLValidator()`. The embedded SAML `Response` then receives a validator that delegates signature validation to that outer `ArtifactResponse`. Later, the SP validates the embedded `Response` against metadata selected from the embedded response issuer, not necessarily the artifact issuer. The critical issue is that `SOAPClient::validateSSL()` returns normally when the TLS public key does not match the key currently being validated. `SAML2\Message::validate()` treats any validator call that does not throw an exception as successful. As a result, an `ArtifactResponse` obtained from one IdP can validate an unsigned embedded SAML `Response` that claims to be issued by a different IdP. In a multi-IdP/federation deployment where a malicious or lower-trust IdP can issue an HTTP-Artifact response to an SP, this can allow the attacker to authenticate to the SP as arbitrary users from a higher-trust victim IdP. ## Impact A malicious or lower-trust IdP in the same SP/federation trust set can authenticate to the SP as users from another IdP when HTTP-Artifact is used. The attacker can choose assertion attributes, `NameID`, and session data in the forged unsigned assertion. This is an authentication bypass and identity-provider impersonation issue. In realistic federations, the security boundary between IdPs matters: a compromised or low-assurance IdP should not be able to mint identities for a high-assurance IdP.

CVE-2026-49283 Affected Simplesamlphp/saml2 Versions

6 component(s)
Fixed Versions:
6.2.15.0.64.20.24.19.3
Product / Package Ecosystem Affected Versions Fixed Version
simplesamlphp/saml2
Packagist
≥ 6.0.0
< 6.2.1
6.2.1
simplesamlphp/saml2
Packagist
≥ 5.0.0
< 5.0.6
5.0.6
simplesamlphp/saml2
Packagist
≥ 4.20.0
< 4.20.2
4.20.2
simplesamlphp/saml2-legacy
Packagist
≥ 4.20.0
< 4.20.2
4.20.2
simplesamlphp/saml2
Packagist
< 4.19.3
4.19.3
simplesamlphp/saml2-legacy
Packagist
< 4.19.3
4.19.3

References

Frequently Asked Questions

What is CVE-2026-49283?
CVE-2026-49283 is a security vulnerability in Simplesamlphp/saml2 involving SimpleSAMLphp HTTP-Artifact TLS validator confusion allows cross-IdP authentication bypass under CWE-295: Improper Certificate Validation.
Which Simplesamlphp/saml2 versions are affected?
Affected versions include releases prior to 6.2.1, 5.0.6, 4.20.2, 4.19.3 across affected packages: simplesamlphp/saml2, simplesamlphp/saml2-legacy.
What version fixes CVE-2026-49283?
Upgrading to 6.2.1, 5.0.6, 4.20.2, 4.19.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is simplesamlphp/saml2 affected?
Yes, simplesamlphp/saml2 is affected in releases prior to 6.2.1, 5.0.6, 4.20.2, 4.19.3. Upgrade your dependency to 6.2.1, 5.0.6, 4.20.2, 4.19.3 or later.
Is simplesamlphp/saml2-legacy affected?
Yes, simplesamlphp/saml2-legacy is affected in releases prior to 4.20.2, 4.19.3. Upgrade your dependency to 4.20.2, 4.19.3 or later.
What is the CVSS score of CVE-2026-49283?
CVE-2026-49283 has a CVSS v3.1 base score of 8.7 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N.
What CWE is associated with CVE-2026-49283?
CVE-2026-49283 is classified under CWE-295: Improper Certificate Validation (The product does not validate, or incorrectly validates, a certificate.).
How can I check Packagist dependencies for CVE-2026-49283?
Run the dependency tree command: 'inspect dependencies for simplesamlphp/saml2'. 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-6929-8p9f-26jx",
  "modified" : "2026-08-04T21:23:56Z",
  "published" : "2026-07-02T20:25:56Z",
  "aliases" : [ "CVE-2026-49283" ],
  "summary" : "SimpleSAMLphp HTTP-Artifact TLS validator confusion allows cross-IdP authentication bypass",
  "details" : "## Summary\n\nSimpleSAMLphp's HTTP-Artifact receive path can treat an unsigned embedded SAML `Response` as cryptographically valid for the wrong IdP.\n\nIn the `HTTPArtifact::receive()` flow, the SOAP `ArtifactResponse` receives a TLS-based validator from `SOAPClient::addSSLValidator()`. The embedded SAML `Response` then receives a validator that delegates signature validation to that outer `ArtifactResponse`. Later, the SP validates the embedded `Response` against metadata selected from the embedded response issuer, not necessarily the artifact issuer.\n\nThe critical issue is that `SOAPClient::validateSSL()` returns normally when the TLS public key does not match the key currently being validated. `SAML2\\Message::validate()` treats any validator call that does not throw an exception as successful. As a result, an `ArtifactResponse` obtained from one IdP can validate an unsigned embedded SAML `Response` that claims to be issued by a different IdP.\n\nIn a multi-IdP/federation deployment where a malicious or lower-trust IdP can issue an HTTP-Artifact response to an SP, this can allow the attacker to authenticate to the SP as arbitrary users from a higher-trust victim IdP.\n\n## Impact\n\nA malicious or lower-trust IdP in the same SP/federation trust set can authenticate to the SP as users from another IdP when HTTP-Artifact is used. The attacker can choose assertion attributes, `NameID`, and session data in the forged unsigned assertion.\n\nThis is an authentication bypass and identity-provider impersonation issue. In realistic federations, the security boundary between IdPs matters: a compromised or low-assurance IdP should not be able to mint identities for a high-assurance IdP.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "simplesamlphp/saml2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "6.0.0"
      }, {
        "fixed" : "6.2.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "simplesamlphp/saml2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "5.0.0"
      }, {
        "fixed" : "5.0.6"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "simplesamlphp/saml2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.20.0"
      }, {
        "fixed" : "4.20.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "simplesamlphp/saml2-legacy"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.20.0"
      }, {
        "fixed" : "4.20.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "simplesamlphp/saml2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.19.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "simplesamlphp/saml2-legacy"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.19.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/simplesamlphp/saml2/security/advisories/GHSA-6929-8p9f-26jx"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/simplesamlphp/saml2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-295" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-02T20:25:56Z",
    "nvd_published_at" : null
  }
}