Vulnerability Database · Hex · esaml · Version
esaml 3.2.0
3.2.0 is affected by 5 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 0 High 3 Medium 2 Low 0 Unrated 0
-
Released 17 Nov 2017
Also known from other sources 0
Newer releases 16
Database updated 23/Oct/2026
Release and licence data published by hex.pm. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
esaml 3.2.0 vulnerabilities
5 vulnerabilities cover esaml 3.2.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2026-93471: esaml Unbounded SAML Message Decompression Leading to Memory Exhaustion | 8.7 high | No fix published | 22 Oct 2026 |
| CVE-2026-105270: esaml Package Atom Table Exhaustion Vulnerability | 8.7 high | No fix published | 22 Oct 2026 |
| CVE-2026-86696: esaml Package Atom Table Exhaustion via Unsigned LogoutResponse | 8.2 high | No fix published | 22 Oct 2026 |
| CVE-2026-28809: esaml XXE Vulnerability Allows Local File Disclosure and SSRF | 6.3 medium | No fix published | 23 Mar 2026 |
| CVE-2026-28809: esaml SAML Library XXE Vulnerability Leading to Local File Read and SSRF | 6.3 medium | No fix published | 23 Mar 2026 |
Looking for another version, or everything Vulert holds for esaml?
Questions
About esaml 3.2.0
Is esaml 3.2.0 vulnerable?
Yes. 5 vulnerabilities in the Vulert database cover esaml 3.2.0: 0 critical, 3 high, 2 medium and 0 low. Each entry above names the fixed version to move to.
Is 3.2.0 the latest release of esaml?
No. 3.2.0 was published 17 Nov 2017, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor esaml for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the esaml version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.