VulertSecurity VulertSecurity

Vulnerability Database · Hex · Package report

esaml: vulnerability history, versions and safety

esaml is a package in the Hex ecosystem. Vulert records 5 vulnerabilities for it across 16 releases, from Mar 2026 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded M1 U4
i
5 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
5 in the last 12 months

Most recent disclosure 22 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all esaml vulnerabilities

Vulert verdict on esaml 4.6.0 i

Updated on 22 Oct 2026

Careful: 4.6.0 has 5 known vulnerabilities, and 5 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 50/100
  • Security Some issues to review
  • Maintenance Maintaining
  • Popularity Key ecosystem project
  • Community Not enough data

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 4.6.0 — affected i
  • Vulnerabilities on record 5 over 1 year · 5 in the last year i
  • Latest disclosure 22 Oct 2026 i
  • Highest CVSS 8.7 i
  • With no published fix 5 i
  • Depended on by 3,068,178 packages i
  • Last release 32 months ago i

Version list, release dates, licence and dependants published by hex.pm, refreshed 22 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for esaml, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
4.6.0 29 Jan 2024 M1 U4 — No Details →
4.5.0 03 Jan 2023 M1 U4 — No Details →
4.4.0 05 Mar 2022 M1 U4 — No Details →
4.3.0 13 Jan 2022 M1 U4 — No Details →
4.2.0 10 Feb 2019 M1 U4 — No Details →
4.1.0 31 Jan 2019 M1 U4 — No Details →
4.0.0 22 Dec 2018 M1 U4 — No Details →
3.7.0 13 Feb 2019 M1 U4 — No Details →
3.6.1 19 Oct 2018 M1 U4 — No Details →
3.6.0 18 Sep 2018 M1 U4 — No Details →
3.5.0 23 Jul 2018 M1 U4 — No Details →
3.4.0 24 Feb 2018 M1 U4 — No Details →
3.3.0 01 Dec 2017 M1 U4 — No Details →
3.2.0 17 Nov 2017 M1 U4 — No Details →
3.1.0 02 Oct 2017 M1 U4 — No Details →
3.0.1 30 Aug 2017 M1 U4 — No Details →

All 16 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 5

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 5 of the 5 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for esaml

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-105270: esaml Package Atom Table Exhaustion Vulnerability 8.7 high No fix published 22 Oct 2026
CVE-2026-93471: esaml Unbounded SAML Message Decompression Leading to Memory Exhaustion 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 SAML Library XXE Vulnerability Leading to Local File Read and SSRF 6.3 medium No fix published 23 Mar 2026
CVE-2026-28809: esaml XXE Vulnerability Allows Local File Disclosure and SSRF 6.3 medium No fix published 23 Mar 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About esaml

Is esaml safe to use?

Vulert records 5 vulnerabilities for esaml in Hex: 0 critical, 0 high, 1 medium and 0 low, plus 4 not yet rated. 5 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is esaml's Vulert package health score?

Vulert scores esaml 50/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of esaml affected?

Yes. 4.6.0, the version you would install today, has 5 known vulnerabilities, and 5 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does esaml have?

5 vulnerabilities are recorded for esaml in the Hex ecosystem: 0 critical, 0 high, 1 medium and 0 low, plus 4 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new esaml vulnerabilities disclosed?

5 vulnerabilities were recorded for esaml in the last 12 months, and the oldest entry in this database dates to 23 Mar 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of esaml are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.