CVE-2026-47079

LOWPre-NVD 2.12.1—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (7th percentile of EPSS-scored CVEs). 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, secondary
Elevated
2.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 2.1Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Inappropriate Encoding for Output Context vulnerability in joshnuss xml_builder (XmlBuilder module) allows Content Spoofing, Cross-site Scripting.

This vulnerability is associated with program files lib/xml_builder.ex and program routines XmlBuilder.generate/1, XmlBuilder.generate/2, XmlBuilder.escape_string/1, XmlBuilder.escape_entity/1.

XmlBuilder.generate/1 does not escape literal & characters in text or attribute values when they are followed by an entity-like token (lt;, gt;, amp;, quot;, apos;). As a result, attacker-supplied input such as <script> is emitted verbatim into the serialized XML rather than being escaped to &lt;script&gt;. When a downstream XML parser later reads the document, it decodes the entity sequences into the literal characters , promoting inert-looking text into real markup. This allows an attacker to bypass upstream filters that block raw < and > characters, injecting markup into any downstream consumer that parses the produced XML and renders the text content in a markup-sensitive context (HTML, SVG, RSS/Atom feeds). Both element text and attribute values are affected.

This issue affects xml_builder: from 0.0.6 before 2.4.1.

CVSS v3
2.1
EG Score
2.1LOWmedium confidence
EG Risk
25
EG Risk 25/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity21% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
7th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 21, 2026

Last Modified

August 24, 2026

References (5)

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFix by version rangeDependents
xml_builder0.0.6 ... 2.4.0 (15 versions)
  • 0.0.6 up to 2.4.1: fixed in 2.4.1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

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

Related CVEs(same product + same CWE)

Same product

2 shown

Hex:xml_builder

Frequently asked(5)

What is CVE-2026-47079?
CVE-2026-47079 is a low vulnerability published on August 21, 2026. Inappropriate Encoding for Output Context vulnerability in joshnuss xml_builder (XmlBuilder module) allows Content Spoofing, Cross-site Scripting. This vulnerability is associated with program files lib/xmlbuilder.ex and program routines XmlBuilder.generate/1, XmlBuilder.generate/2,…
When was CVE-2026-47079 disclosed?
CVE-2026-47079 was first published on August 21, 2026, with the most recent update on August 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47079 actively exploited?
CVE-2026-47079 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47079?
CVE-2026-47079 has a CVSS base score of 2.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47079?
A fix for CVE-2026-47079 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47079

Explore →

Is Your Infrastructure Affected by CVE-2026-47079?

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

Book a Demo →Browse All CVEs