NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
💧
💧 Hex
Not in CISA KEV
HIGH severity

CVE-2019-15160 — sweet_xml

HIGH

CVE-2019-15160 is a high-severity (CVSS 7.5) CWE-776 vulnerability in sweet_xml. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for sweet_xml — see the affected versions and patch details below.

Inline DTD allows XML bomb attack

Also known asGHSA-qpmc-wprv-x746
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs77th percentile — riskier than 77% of all scored CVEsHighest risk
0.00%0.72%1.45%2.17%0.3%1.7%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
💧sweet_xml

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Hex packages — download data is not available via public APIs for these ecosystems.

Description

The SweetXml (aka sweet_xml) package through 0.6.6 for Erlang and Elixir allows attackers to cause a denial of service (resource consumption) via an XML entity expansion attack with an inline DTD.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
💧Hexsweet_xmlall versions0.7.0mix deps.update sweet_xml

Affected Products

1 product · 1 configurations
Application
sweet xmlkbrw
≤ 0.6.6
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The SweetXml (aka sweet_xml) package through 0.6.6 for Erlang and Elixir…

github.comNVDJul 2021

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sweet_xml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update sweet_xml to 0.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-15160 is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

The SweetXml (aka sweet_xml) package through 0.6.6 for Erlang and Elixir allows attackers to cause a denial of service (resource consumption) via an XML entity expansion attack with an inline DTD.
O3 Security · Impact-Aware SCA

Is CVE-2019-15160 in your dependencies?

Find it across Hex, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2019-15160: sweet_xml DoS — Fixed in 0.7.0