Loading vulnerability…
CVE-2015-1796 is an improper certificate-validation flaw in the PKIX trust engines of OpenSAML Java before 2.6.5 and Shibboleth Identity Provider before 2.4.4. When no trusted names are available for an entityID, the affected trust logic can accept an X.509 credential rather than rejecting it for lacking an authorized identity binding. A certificate issued by a shibmd:KeyAuthority trust anchor can consequently be accepted for an entity other than the certificate holder, within that KeyAuthority's scope.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A PKIX trust-validation flaw enabling an attacker with a certificate issued by a shibmd:KeyAuthority trust anchor to impersonate an entity in that keyAuthority's scope.
A PKIX trust-validation flaw that can trust an X.509 credential when no trusted names exist for an entityID, enabling impersonation using a certificate issued by a shibmd:KeyAuthority trust anchor.
A PKIX trust-validation flaw that can trust an X.509 credential when no trusted names exist for an entityID, enabling impersonation using a certificate issued by a shibmd:KeyAuthority trust anchor.
A PKIX trust-validation flaw that can trust an X.509 credential when no trusted names exist for an entityID, enabling impersonation using a certificate issued by a shibmd:KeyAuthority trust anchor.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.