CVE-2016-10127

CRITICALNVD 9.09.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.0 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 35% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 2%CVSS: 9.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

PySAML2 allows remote attackers to conduct XML external entity (XXE) attacks via a crafted SAML XML request or response.

CVSS v3
9.0
EG Score
9.0(medium)
EPSS
79.8%
KEV
Not listed

Published

March 3, 2017

Last Modified

May 13, 2026

Advisory Details (6)

Auto-updated May 22, 2026
🔬 Proof of concept available. Patch available.
generic

Fix XXE in XML parsing (related to #366) · IdentityPython/pysaml2@6e09a25 · GitHub

https://github.com/rohe/pysaml2/commit/6e09a25d9b4b7aa7a506853210a9a14100b8bc9b
generic Patch Available

#850716 - python-pysaml2: CVE-2016-10149 - Debian Bug report logs

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850716
generic
http://www.securityfocus.com/bid/95376
generic

oss-security - Re: CVE request: python-pysaml2 XML external entity attack

http://www.openwall.com/lists/oss-security/2017/01/19/5
generic

Fix XXE in XML parsing (related to #366) by fruechel · Pull Request #379 · IdentityPython/pysaml2 · GitHub

https://github.com/rohe/pysaml2/pull/379
generic🟡 PoC Available

PySAML vulnerable to XXE · Issue #366 · IdentityPython/pysaml2 · GitHub

https://github.com/rohe/pysaml2/issues/366

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
pysaml20.4.3 ... 4.4.0 (23 versions)4.5.0—

Data Freshness Timeline

(refreshed 10× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-12 05:42 UTCEPSS rescore
  2. 2026-07-12 02:41 UTCOSV refresh
  3. 2026-07-11 08:23 UTCEPSS rescore
  4. 2026-07-09 19:05 UTCEPSS rescore
  5. 2026-07-09 19:05 UTCEPSS rescore
  6. 2026-07-08 15:10 UTCEPSS rescore
  7. 2026-07-07 13:42 UTCEPSS rescore
  8. 2026-07-07 13:42 UTCEPSS rescore
  9. 2026-07-06 16:24 UTCEPSS rescore
  10. 2026-07-06 02:20 UTCEPSS rescore
  11. 2026-07-05 02:26 UTCEPSS rescore
  12. 2026-07-04 06:28 UTCEPSS rescore
  13. 2026-07-01 15:02 UTCEPSS rescore
  14. 2026-06-30 23:19 UTCEPSS rescore
  15. 2026-06-30 23:19 UTCEPSS rescore
  16. 2026-06-28 14:04 UTCEPSS rescore
  17. 2026-06-28 04:53 UTCEPSS rescore
  18. 2026-06-27 03:05 UTCEPSS rescore
  19. 2026-06-25 13:47 UTCEPSS rescore
  20. 2026-06-25 13:47 UTCEPSS rescore
  21. 2026-06-24 14:02 UTCEPSS rescore
  22. 2026-06-24 14:02 UTCEPSS rescore
  23. 2026-06-23 21:30 UTCEPSS rescore
  24. 2026-06-23 09:00 UTCOSV refresh
  25. 2026-06-21 14:54 UTCEPSS rescore
Show 54 more
  1. 2026-06-21 14:54 UTCEPSS rescore
  2. 2026-06-21 01:57 UTCEPSS rescore
  3. 2026-06-21 01:57 UTCEPSS rescore
  4. 2026-06-19 19:23 UTCEPSS rescore
  5. 2026-06-19 19:23 UTCEPSS rescore
  6. 2026-06-18 17:50 UTCEPSS rescore
  7. 2026-06-17 17:50 UTCEPSS rescore
  8. 2026-06-17 17:49 UTCEPSS rescore
  9. 2026-06-16 17:50 UTCEPSS rescore
  10. 2026-06-16 17:50 UTCEPSS rescore
  11. 2026-06-15 17:45 UTCEPSS rescore
  12. 2026-06-14 23:14 UTCEPSS rescore
  13. 2026-06-13 22:57 UTCEPSS rescore
  14. 2026-06-12 23:09 UTCEPSS rescore
  15. 2026-06-12 23:09 UTCEPSS rescore
  16. 2026-06-11 13:57 UTCEPSS rescore
  17. 2026-06-11 13:57 UTCEPSS rescore
  18. 2026-06-10 22:15 UTCEPSS rescore
  19. 2026-06-10 13:18 UTCEPSS rescore
  20. 2026-06-08 14:14 UTCEPSS rescore
  21. 2026-06-07 15:22 UTCEPSS rescore
  22. 2026-06-06 13:45 UTCEPSS rescore
  23. 2026-06-06 08:33 UTCOSV refresh
  24. 2026-06-05 22:44 UTCEPSS rescore
  25. 2026-06-05 06:08 UTCEPSS rescore
  26. 2026-06-05 06:08 UTCEPSS rescore
  27. 2026-06-04 13:10 UTCEPSS rescore
  28. 2026-06-04 13:10 UTCEPSS rescore
  29. 2026-06-02 20:10 UTCEPSS rescore
  30. 2026-06-01 13:49 UTCEPSS rescore
  31. 2026-06-01 13:49 UTCEPSS rescore
  32. 2026-05-31 22:28 UTCEPSS rescore
  33. 2026-05-31 22:28 UTCEPSS rescore
  34. 2026-05-31 00:14 UTCEPSS rescore
  35. 2026-05-29 13:41 UTCEPSS rescore
  36. 2026-05-28 13:42 UTCEPSS rescore
  37. 2026-05-28 13:42 UTCEPSS rescore
  38. 2026-05-27 13:38 UTCEPSS rescore
  39. 2026-05-27 13:38 UTCEPSS rescore
  40. 2026-05-26 13:41 UTCEPSS rescore
  41. 2026-05-26 07:16 UTCEPSS rescore
  42. 2026-05-26 07:16 UTCEPSS rescore
  43. 2026-05-24 16:43 UTCEPSS rescore
  44. 2026-05-23 00:10 UTCEG score recompute
  45. 2026-05-22 21:15 UTCEPSS rescore
  46. 2026-05-22 15:46 UTCEG score recompute
  47. 2026-05-21 22:40 UTCEPSS rescore
  48. 2026-05-20 22:37 UTCEPSS rescore
  49. 2026-05-20 22:37 UTCEPSS rescore
  50. 2026-05-20 11:21 UTCEPSS rescore
  51. 2026-05-20 11:21 UTCEPSS rescore
  52. 2026-05-20 11:21 UTCEPSS rescore
  53. 2026-05-18 21:30 UTCEPSS rescore
  54. 2026-05-18 21:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2016-10127?
CVE-2016-10127 is a critical vulnerability published on March 3, 2017. PySAML2 allows remote attackers to conduct XML external entity (XXE) attacks via a crafted SAML XML request or response.
When was CVE-2016-10127 disclosed?
CVE-2016-10127 was first published in the National Vulnerability Database on March 3, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-10127 actively exploited?
CVE-2016-10127 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 79.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-10127?
CVE-2016-10127 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2016-10127?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-10127, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-10127

Explore →

Is Your Infrastructure Affected by CVE-2016-10127?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs