https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-04T11:55:13.958782+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/certfr-2025-avi-0836 certfr-2025-avi-0836 — De multiples vulnérabilités ont été découvertes dans Tenable Security Center. Elles permettent à un attaquant de provoq… 2026-10-04T11:55:14.024130+00:00 certfr-2025-avi-0836 https://cve.radiocsirt.org/vuln/euvd-2026-238779 EUVD-2026-238779 2026-10-04T11:55:14.024175+00:00 EUVD-2026-238779 https://cve.radiocsirt.org/vuln/fkie_cve-2025-27773 fkie_cve-2025-27773 2026-10-04T11:55:14.024190+00:00

The SimpleSAMLphp SAML2 library is a PHP library for SAML2 related functionality. Prior to versions 4.17.0 and 5.0.0-alpha.20, there is a signature confusion attack in the HTTPRedirect binding. An attacker with any signed SAMLResponse via the HTTP-Redirect binding can cause the application to accept an unsigned message. Versions 4.17.0 and 5.0.0-alpha.20 contain a fix for the issue.

 https://cve.radiocsirt.org/vuln/ghsa-46r4-f8gj-xg56 GHSA-46r4-f8gj-xg56 — The SimpleSAMLphp SAML2 library incorrectly verifies signatures for HTTP-Redirect binding 2026-10-04T11:55:14.024221+00:00

Affected: Packagist: simplesamlphp/saml2, Packagist: simplesamlphp/saml2-legacy

### Summary There's a signature confusion attack in the HTTPRedirect binding. An attacker with any signed SAMLResponse via the HTTP-Redirect binding can cause the application to accept an unsigned message.

I believe that it exists for v4 only. I have not yet developed a PoC.

V5 is well designed and instead builds the signed query from the same message that will be consumed. ### Details

#### What is verified The data['SignedQuery'] is the string that will be verified by the public key.

It is defined here: https://github.com/simplesamlphp/saml2/blob/9545abd0d9d48388f2fa00469c5c1e0294f0303e/src/SAML2/HTTPRedirect.php#L178-L217

THe code will iterate through each parameter name. Notably, sigQuery is overridden each time when processing, making the last of SAMLRequest/SAMLResponse used for sigQuery.

For example, given:

SAMLRequest=a&SAMLResponse=idpsigned

SAMLResponse=idpsigned will be set as sigQuery, then later verified

#### What is actually processed

Processing uses SAMLRequest parameter value first, (if it exists) then SAMLResponse:

https://github.com/simplesamlphp/saml2/blob/9545abd0d9d48388f2fa00469c5c1e0294f0303e/src/SAML2/HTTPRedirect.php#L104-L113

Given this, the contents that are processed might not be the same as the data that is actually verified.

### Exploiting Suppose an attacker has a signed HTTP Redirect binding from IdP, say a signed logout response. :

SAMLResponse=idpsigned&RelayState=...&SigAlg=...&Signature

Then an attacker can append SAMLReq…

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-27773 UBUNTU-CVE-2025-27773 2026-10-04T11:55:14.024281+00:00

Affected: Ubuntu:Pro:16.04:LTS: simplesamlphp, Ubuntu:Pro:18.04:LTS: simplesamlphp, Ubuntu:Pro:20.04:LTS: simplesamlphp, Ubuntu:Pro:22.04:LTS: simplesamlphp, Ubuntu:24.04:LTS: simplesamlphp, Ubuntu:25.10: simplesamlphp

The SimpleSAMLphp SAML2 library is a PHP library for SAML2 related functionality. Prior to versions 4.17.0 and 5.0.0-alpha.20, there is a signature confusion attack in the HTTPRedirect binding. An attacker with any signed SAMLResponse via the HTTP-Redirect binding can cause the application to accept an unsigned message. Versions 4.17.0 and 5.0.0-alpha.20 contain a fix for the issue.