Skip to main content
Menu
CVEs

CVE

Simplesamlphp SAML2 auth bypass in HTTP-Artifact message signature checks

CVE-2026-110782EUVD-2026-127138

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N

8.7HighCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 6.2.4, 7.0.0-rc2
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 6.2.4, 7.0.0-rc2.

Published
Last modified
Reference
Last checked
42/100 · provisional
Unclear
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: poc
  • Automatable: no
  • Technical impact: total

Summary

The SimpleSAMLphp SAML2 library, a PHP library for SAML2 functionality, can be bypassed by an attacker who controls one trusted identity provider in a multi-IdP federation. That attacker can return an unsigned SAML Response claiming to come from a different identity provider, which skips the HTTP-Artifact binding's check of embedded messages. The attack can be carried out remotely, without logging in and without any user action.

Written by a model from the sources below. Verify against them.

Original description

The SimpleSAMLphp SAML2 library is a PHP library for SAML2 related functionality. From 6.2.2 until 6.2.4 and 7.0.0-rc2, HTTPArtifact::receive() in src/Binding/HTTPArtifact.php verifies a signed outer ArtifactResponse but returns an unsigned embedded SAML Response before calling verifyMessageSignature(). The signed path verifies with the artifact issuer's metadata keys without requiring the embedded Response issuer to match that artifact issuer. In a multi-IdP federation, an attacker controlling one trusted IdP can therefore return a validly signed outer ArtifactResponse containing an unsigned Response that claims a different IdP, bypassing the binding's embedded-message authentication. End-to-end impersonation requires a service provider using HTTP-Artifact and a downstream consumer that relies on the binding to authenticate the embedded Response rather than independently requiring a signature. This issue is fixed in versions 6.2.4 and 7.0.0-rc2.

Who should check

Teams running simplesamlphp/saml2 6.2.2 to 6.2.3 or 7.0.0 before rc1 as a service provider using the HTTP-Artifact binding in a multi-IdP federation.

“SP uses the HTTP-Artifact binding in a multi-IdP federation”

github.com

cve.now Index

42Pcve.now Index 42 of 100 · methodology v3 · provisional
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.7/10CVSS 8.7, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 72 if added to CISA KEV
  • Would score about 67 if CISA's SSVC rates exploitation active
  • Would score about 47 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 6.2.4, 7.0.0-rc2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-110782 (SAML2: Incomplete fix of CVE-2026-49283: unsigned embedded Response bypasses HTTP-Artifact signature verification (no embedded-Issuer…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-110782 (entry last updated 2026-11-17):
Affected:
- simplesamlphp saml2: from 6.2.2, fixed in 6.2.4; from 7.0.0-rc1, fixed in 7.0.0-rc2
Fixed versions: 6.2.4, 7.0.0-rc2.
Conditions (all must be true for the bug to be hit):
- Affected versions are 6.2.2 through 6.2.3, and 7.0.0 before rc1. (source: https://github.com/simplesamlphp/saml2/security/advisories/GHSA-r7hw-jx6r-756g)
- Service provider uses the HTTP-Artifact binding in a multi-IdP federation. (source: https://github.com/simplesamlphp/saml2/security/advisories/GHSA-r7hw-jx6r-756g)
- A downstream consumer relies on the binding to authenticate the embedded Response rather than requiring its own signature. (source: https://github.com/simplesamlphp/saml2/security/advisories/GHSA-r7hw-jx6r-756g)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-110782 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-110782 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/simplesamlphp/saml2/security/advisories/GHSA-r7hw-jx6r-756g
- https://github.com/simplesamlphp/saml2/commit/7b7fbb5322cb5607db3e5a329681f4886b1449fe
- https://github.com/simplesamlphp/saml2/commit/9a21edb96de1f3ece3b40ccbe3b7de761917a06f
- https://github.com/simplesamlphp/saml2/releases/tag/v6.2.4
- https://github.com/simplesamlphp/saml2/releases/tag/v7.0.0-rc2
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-110782
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-110782"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • simplesamlphp saml2

    From 6.2.2 · fixed in 6.2.4; From 7.0.0-rc1 · fixed in 7.0.0-rc2

Evidence 7

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 4

  1. Repository
  2. Repository
  3. Repository
  4. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-110782

Is CVE-2026-110782 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The SAML library accepts an embedded Response inside an HTTP-Artifact flow without its own signature, relying on the binding to authenticate it. An attacker who controls one trusted identity provider can return an unsigned Response that claims another provider's identity, which is accepted as received and allows impersonating a user at that other provider.Source: github.com

Which versions are affected by CVE-2026-110782?

saml2: from 6.2.2 before 6.2.4; from 7.0.0-rc1 before 7.0.0-rc2.Source: cve.now feed data

Am I affected, and how do I check?

The advisory's text lists versions 6.2.2 through 6.2.3 and 7.0.0 before rc1. The setup is a service provider that uses the HTTP-Artifact binding in a multi-IdP federation, with a downstream consumer that relies on the binding instead of requiring its own signature. The installed simplesamlphp/saml2 version can be checked in composer.lock or with composer show simplesamlphp/saml2.Source: github.com

How do I fix CVE-2026-110782?

Upgrade simplesamlphp/saml2 to 6.2.4 for the 6.2 line or to 7.0.0-rc2 for the 7.0 line. This advisory is an incomplete fix of CVE-2026-49283, so the earlier fix alone does not close this issue.Source: github.com

More CVEs