CVE intelligence and bounded remediation

CVE-2026-28809 — Arekinath Esaml security vulnerability

Medium CVSS 6.3

XML External Entity (XXE) vulnerability in esaml (and its forks) allows an attacker to cause the system to read local files and incorporate their contents into processed SAML documents, and potentially perform SSRF via crafted SAML messages. esaml parses attacker-controlled SAML messages using xmerl_scan:string/2 before signature verification without disabling XML entity expansion. On Erlang/OTP versions before 27, Xmerl allows entities by default, enabling pre-signature XXE attacks. An attacker can cause the host to read local files (e.g., Kubernetes-mounted secrets) into the SAML document. If the attacker is not a trusted SAML SP, signature verification will fail and the document is discarded, but file contents may still be exposed through logs or error messages. This issue affects all versions of esaml, including forks by arekinath, handnot2, and dropbox. Users running on Erlang/OTP 27 or later are not affected due to Xmerl defaulting to entities disabled.

Severity
Medium
CVSS
6.3 (4.0)
Published
2026-03-23
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-611

Affected products

  • arekinath / esaml
  • dropbox / esaml
  • handnot2 / esaml
  • jump-app / esaml

Matched remediation archetype

XML external entity and unsafe XML processing

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Inventory XML parsers used by APIs, file imports, office or image formats, identity protocols, feeds, and background jobs.
  • Determine whether document type declarations, external entities, XInclude, schemas, or network resolvers are enabled.
  • Map parser filesystem and network access and the sensitivity of documents it processes.

Remediate safely

  • Configure each parser to reject document type declarations and disable external entity, XInclude, and network resolution features.
  • Prefer a data format or hardened parser that does not support external resolution, and apply input size and depth limits.
  • Update affected XML libraries and centralize secure parser construction so callers cannot silently override it.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.