Exposure of Sensitive Information to an Unauthorized Actor in OpenSAML

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2013-6440: 2.75% estimated exploitation activity in the next 30 days; percentile 86.24 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

The (1) BasicParserPool, (2) StaticBasicParserPool, (3) XML Decrypter, and (4) SAML Decrypter in Shibboleth OpenSAML-Java before 2.6.1 set the expandEntityReferences property to true, which allows remote attackers to conduct XML external entity (XXE) attacks via a crafted XML DOCTYPE declaration.

Published by the source

13 May 2022, 01:04 UTC

Last modified by the source

27 Jan 2023, 05:02 UTC

Source last checked

26 Oct 2026, 16:00 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-v723-58jv-2qc4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2013-6440

Advisory: Exposure of Sensitive Information to an Unauthorized Actor in OpenSAML
IDs: CVE-2013-6440, GHSA-v723-58jv-2qc4
Record: https://patchnext.com/advisories/cve-2013-6440 (revision 1, source checked 26 Oct 2026, 16:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.opensaml:opensaml 2.6.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.opensaml:opensaml: affected < 2.6.1; fixed in 2.6.1

## Suggested inspection (read-only)
- Maven org.opensaml:opensaml: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.opensaml:opensaml.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-v723-58jv-2qc4 (GitHub-reviewed advisory GHSA-v723-58jv-2qc4 lists affected ranges: Maven org.opensaml:opensaml >=0 <2.6.1)

Commands are suggestions: review each one before running it.