# Improper Certificate Validation in Shibboleth Identity Provider and OpenSAML

Advisory record · `GHSA-78fq-w796-q537`

- **Identifiers:** `GHSA-78fq-w796-q537` · `CVE-2015-1796`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-295](https://cwe.mitre.org/data/definitions/295.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 17 May 2022
- **Updated:** 7 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 May 2022, 03:38 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.opensaml:opensaml` (Maven): affected `<2.6.5`; fixed in `2.6.5`
- `edu.internet2.middleware:shibboleth-identityprovider` (Maven): affected `<2.4.4`; fixed in `2.4.4`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Two packages are affected: org.opensaml:opensaml before 2.6.5 and edu.internet2.middleware:shibboleth-identityprovider before 2.4.4. The PKIX trust engines in these packages trust candidate X.509 credentials when no trusted names exist for an entityID, so a remote attacker can impersonate an entity using a certificate issued by a shibmd:KeyAuthority trust anchor. Upgrade opensaml to 2.6.5 and shibboleth-identityprovider to 2.4.4 or later.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.012, the 69th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:12 UTC: First seen by agentprime
- 31 Oct 2026, 15:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-78fq-w796-q537)

## Sources

- [GitHub Advisory Database: GHSA-78fq-w796-q537](https://github.com/advisories/GHSA-78fq-w796-q537)
- [OSV: GHSA-78fq-w796-q537](https://osv.dev/vulnerability/GHSA-78fq-w796-q537)
- <https://nvd.nist.gov/vuln/detail/CVE-2015-1796>
- <https://shibboleth.net/community/advisories/secadv_20150225.txt>
- <http://rhn.redhat.com/errata/RHSA-2015-1176.html>
- <http://rhn.redhat.com/errata/RHSA-2015-1177.html>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-78fq-w796-q537>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-78fq-w796-q537/>. Everything for agents: <https://agentprime.io/llms.txt>.
