Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5

Validation of SignedInfo

CVE-2023-49087GHSA-ww7x-3gxh-qm6r

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (simplesamlphp/xml-security 1.6.12; simplesamlphp/saml2 5.0.0-alpha.13), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
  • CVE-2023-49087: 0.19% estimated exploitation activity in the next 30 days; percentile 8.99 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Validation of an XML Signature requires verification that the hash value of the related XML-document (after any optional transformations and/or normalizations) matches a specific DigestValue-value, but also that the cryptografic signature on the SignedInfo-tree (the one that contains the DigestValue) verifies and matches a trusted public key. Within the simpleSAMLphp/xml-security library (https://github.com/simplesamlphp/xml-security), the hash is being validated using SignedElementTrait::validateReference, and the signature is being verified in SignedElementTrait::verifyInternal https://github.com/simplesamlphp/xml-security/blob/master/src/XML/SignedElementTrait.php: What stands out is that the signature is being calculated over the canonical version of the SignedInfo-tree. The validateReference method, however, uses the original non-canonicalized version of SignedInfo. Impact If an attacker somehow (i.e. by exploiting a bug in PHP's canonicalization function) manages to manipulate…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-ww7x-3gxh-qm6r

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-49087

Advisory: Validation of SignedInfo
IDs: CVE-2023-49087, GHSA-ww7x-3gxh-qm6r
Record: https://patchnext.com/advisories/cve-2023-49087 (revision 1, source checked 26 Oct 2026, 14:11 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: simplesamlphp/xml-security 1.6.12; simplesamlphp/saml2 5.0.0-alpha.13. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist simplesamlphp/xml-security: affected >= 1.6.11, <= 1.6.11; fixed in 1.6.12
- Packagist simplesamlphp/saml2: affected >= 5.0.0-alpha.12, <= 5.0.0-alpha.12; fixed in 5.0.0-alpha.13

## Suggested inspection (read-only)
- Packagist simplesamlphp/xml-security: check the installed version with your package manager.
- Packagist simplesamlphp/saml2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on simplesamlphp/xml-security, simplesamlphp/saml2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-ww7x-3gxh-qm6r (GitHub-reviewed advisory GHSA-ww7x-3gxh-qm6r lists affected ranges: Packagist simplesamlphp/xml-security >=1.6.11 =5.0.0-alpha.12 <=5.0.0-alpha.12)

Commands are suggestions: review each one before running it.

Loading voting…