505 matches found
CVE-2026-80200
Kimai before 2.53.0 contains an open redirect vulnerability in the SAML authentication success handler that accepts unvalidated RelayState POST parameters as redirect destinations. Attackers with IdP access can supply malicious RelayState values to redirect authenticated users to...
PT-2026-81913
Name of the Vulnerable Software and Affected Versions Kimai versions prior to 2.53.0 Description An open redirect issue exists in the SAML authentication success handler. The system accepts unvalidated RelayState POST parameters as redirect destinations, allowing attackers with Identity Provider...
CVE-2026-68745
Certificate validation failures in SAML authentication in Apache CloudStack 4.20.3.0 and 4.22.1.0 on all platforms allow a malicious agent to forge a SAML response to the management server. The agent will have to spoof the ip address of the IdP or get an url of its own choosing registered in the...
EUVD-2026-63830
Certificate validation failures in SAML authentication in Apache CloudStack 4.20.3.0 and 4.22.1.0 on all platforms allow a malicious agent to forge a SAML response to the management server. The agent will have to spoof the ip address of the IdP or get an url of its own choosing registered in the...
CVE-2026-68745 Apache CloudStack: SAML2 Signature Validation Silently Skipped for Cert-less IdP
Certificate validation failures in SAML authentication in Apache CloudStack 4.20.3.0 and 4.22.1.0 on all platforms allow a malicious agent to forge a SAML response to the management server. The agent will have to spoof the ip address of the IdP or get an url of its own choosing registered in the...
CVE-2026-68745
Certificate validation failures in SAML authentication in Apache CloudStack 4.20.3.0 and 4.22.1.0 on all platforms allow a malicious agent to forge a SAML response to the management server. The agent will have to spoof the ip address of the IdP or get an url of its own choosing registered in the...
CVE-2026-68745
Apache CloudStack versions 4.20.3.0 and 4.22.1.0 are vulnerable to certificate validation failures within the SAML authentication process. This flaw allows a malicious agent to forge a SAML response to the management server by either spoofing the Identity Provider (IdP) IP address or registering ...
PT-2026-79333
Certificate validation failures in SAML authentication in Apache CloudStack 4.20.3.0 and 4.22.1.0 on all platforms allow a malicious agent to forge a SAML response to the management server. The agent will have to spoof the ip address of the IdP or get an url of its own choosing registered in the...
CVE-2026-68745: Improper Verification of Cryptographic Signature
Certificate validation failures in SAML authentication in Apache CloudStack 4.20.3.0 and 4.22.1.0 on all platforms allow a malicious agent to forge a SAML response to the management server. The agent will have to spoof the ip address of the IdP or get an url of its own choosing registered in the...
CVE-2026-23933
In Zabbix 7.4 the cryptographic key used for signing Frontend sessions has been erroneously written to the database seed. Currently the only known exploitation scenario is for deployments that utilize both - SAML authentication and guest users. In such cases the key can be used to forge valid...
EUVD-2026-60737
In Zabbix 7.4 the cryptographic key used for signing Frontend sessions has been erroneously written to the database seed. Currently the only known exploitation scenario is for deployments that utilize both - SAML authentication and guest users. In such cases the key can be used to forge valid...
CVE-2026-23933
In Zabbix 7.4 , a cryptographic key used for signing Frontend sessions was erroneously written to the database seed. This vulnerability specifically impacts deployments utilizing both SAML authentication and guest users , where the key can be used to forge valid session cookies, potentially leadi...
CVE-2026-23933: Use of Hard-coded Password
In Zabbix 7.4 the cryptographic key used for signing Frontend sessions has been erroneously written to the database seed. Currently the only known exploitation scenario is for deployments that utilize both - SAML authentication and guest users. In such cases the key can be used to forge valid...
PT-2026-76959
Name of the Vulnerable Software and Affected Versions Zabbix version 7.4 Description The cryptographic key used for signing Frontend sessions is incorrectly written to the database seed. This issue affects deployments that simultaneously use SAML authentication and guest users, allowing the key t...
CVE-2026-61979
Unauthenticated Privilege Escalation in SAML SP Single Sign On = 5.4.3 versions...
CVE-2026-7557 SAML authentication bypass in Progress MarkLogic Server
An improper verification of cryptographic signature vulnerability in the SAML authentication module of Progress MarkLogic Server before 11.3.6 and 12.0.3 allows an unauthenticated remote attacker to bypass authentication and impersonate any user, including administrators. This vulnerability affec...
CVE-2026-7557
An vulnerability summary for CVE-2026-7557: The SAML authentication module in Progress MarkLogic Server is affected by an improper verification of cryptographic signature. This allows an unauthenticated remote attacker to bypass authentication and impersonate any user (including administrators) i...
PT-2026-68215
Name of the Vulnerable Software and Affected Versions Progress MarkLogic Server versions prior to 11.3.6 Progress MarkLogic Server versions prior to 12.0.3 Description An improper verification of cryptographic signature in the SAML authentication module allows an unauthenticated remote attacker t...
CVE-2026-7557: Improper Verification of Cryptographic Signature
An improper verification of cryptographic signature vulnerability in the SAML authentication module of Progress MarkLogic Server before 11.3.6 and 12.0.3 allows an unauthenticated remote attacker to bypass authentication and impersonate any user, including administrators. This vulnerability affec...
CVE-2026-18092
Net::SAML2 versions before 0.86 for Perl allow SAML authentication bypass via XML signature wrapping because newfromxml reads assertion identity with document-wide XPath instead of the signed subtree. newfromxml reads the NameID, attribute values, SessionIndex, audience and other identity fields...