# Exposure of Sensitive Information to an Unauthorized Actor in OpenSAML

Advisory record · `GHSA-v723-58jv-2qc4`

- **Identifiers:** `GHSA-v723-58jv-2qc4` · `CVE-2013-6440`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 13 May 2022
- **Updated:** 5 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 13 May 2022, 01:04 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.1`; fixed in `2.6.1`

## Machine-written summary

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

> The org.opensaml:opensaml package (OpenSAML-Java) is vulnerable in versions before 2.6.1. The BasicParserPool, StaticBasicParserPool, XML Decrypter and SAML Decrypter set expandEntityReferences to true, so a remote attacker who sends crafted XML with a DOCTYPE declaration can carry out XML external entity (XXE) attacks. Upgrade to version 2.6.1 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.028, the 86th 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-v723-58jv-2qc4)

## Sources

- [GitHub Advisory Database: GHSA-v723-58jv-2qc4](https://github.com/advisories/GHSA-v723-58jv-2qc4)
- [OSV: GHSA-v723-58jv-2qc4](https://osv.dev/vulnerability/GHSA-v723-58jv-2qc4)
- <https://nvd.nist.gov/vuln/detail/CVE-2013-6440>
- <https://bugzilla.redhat.com/show_bug.cgi?id=1043332>
- <https://www.oracle.com/security-alerts/cpujan2022.html>
- <http://blog.sendsafely.com/post/69590974866/web-based-single-sign-on-and-the-dangers-of-saml-xml>
- <http://rhn.redhat.com/errata/RHSA-2014-0170.html>
- <http://rhn.redhat.com/errata/RHSA-2014-0171.html>
- <http://rhn.redhat.com/errata/RHSA-2014-0172.html>
- <http://rhn.redhat.com/errata/RHSA-2014-0195.html>
- <http://shibboleth.net/community/advisories/secadv_20131213.txt>

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-v723-58jv-2qc4>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-v723-58jv-2qc4/>. Everything for agents: <https://agentprime.io/llms.txt>.
