CVE-2017-12873

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 27% 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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 2%CVSS: 9.8Exploit: NoneExposed: 0

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

SimpleSAMLphp 1.7.0 through 1.14.10 might allow attackers to obtain sensitive information, gain unauthorized access, or have unspecified other impacts by leveraging incorrect persistent NameID generation when an Identity Provider (IdP) is misconfigured.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
73.8%
KEV
Not listed

Published

September 1, 2017

Last Modified

May 13, 2026

Advisory Details (4)

Auto-updated Jun 22, 2026
Patch available. Sources: github_commit.
generic

[SECURITY] [DSA 4127-1] simplesamlphp security update

https://www.debian.org/security/2018/dsa-4127
generic

SSPSA 201612-04: Incorrect persistent NameID generation - SimpleSAMLphp

https://simplesamlphp.org/security/201612-04
generic Patch Available

[SECURITY] [DLA 1205-1] simplesamlphp security update

https://lists.debian.org/debian-lts-announce/2017/12/msg00007.html
github_commit

commit 90dca8351584 (simplesamlphp/simplesamlphp)

Fix landed in simplesamlphp/simplesamlphp commit 90dca8351584 — awaiting tagged release

https://github.com/simplesamlphp/simplesamlphp/commit/90dca835158495b173808273e7df127303b8b953

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
simplesamlphp/simplesamlphpv1.12.0 ... v1.14.9 (18 versions)1.14.11—

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2017-12873?
CVE-2017-12873 is a critical vulnerability published on September 1, 2017. SimpleSAMLphp 1.7.0 through 1.14.10 might allow attackers to obtain sensitive information, gain unauthorized access, or have unspecified other impacts by leveraging incorrect persistent NameID generation when an Identity Provider (IdP) is misconfigured.
When was CVE-2017-12873 disclosed?
CVE-2017-12873 was first published in the National Vulnerability Database on September 1, 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-2017-12873 actively exploited?
CVE-2017-12873 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 73.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-12873?
CVE-2017-12873 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-12873?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-12873, 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-2017-12873

Explore →

Is Your Infrastructure Affected by CVE-2017-12873?

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

Start Free Scan →Browse All CVEs