vulns.co
/
GKData.io MCP and API Buy me a coffee

samlify

samlify: signing does not establish claim provenance

samlify could turn user-controlled profile text into extra SAML claims before the identity provider signed them. The maintainer's example shows those added attributes being accepted; gaining privileges would also require the receiving application to use them for access decisions. A valid signature cannot make improperly constructed claims trustworthy.

Open the referenceMaintainer AdvisoryReviewed 2026-10-03

How to use this reference

Editorial reasoning: signatures protect the generated representation, not the authority of each input used to construct it. Keep profile text separate from authorization-claim structure, use context-correct serialization before signing, and review which upstream actors may supply claims consumed as roles. A signature check alone cannot repair a compromised issuance boundary.

Before reading

  • SAML issuer/relying-party roles, XML contexts and claim-based authorization

Context and limits

  • The advisory identifies master/v2.10.2 as affected and 2.13.0 as patched; it does not establish a complete affected-version interval. Exposure requires user-controlled values reaching assertion generation and a relying party trusting the resulting attributes.
  • The published example supports added attributes being parsed; downstream privileged application actions are conditional consequences, not evidence of a breached deployment.
  • tngan published the advisory; RootUp is credited as reporter in both advisory and release notes. The 2.13.0 release explicitly references this advisory. Its displayed May 14 timestamp omits the year in retrieved text, so no full patch date is asserted. Resource edition remains null.

Sources

  1. SAML attribute-generation integrity advisorysamlify · reviewed 2026-10-03
  2. Release v2.13.0samlify · reviewed 2026-10-03

Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software