VulnerabilityPublished 30 Oct 2026

CVE-2026-117645: phoenixframework phoenix_html · Cross-site Scripting

Affects phoenixframework phoenix_htmlSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.4.0 or 3.3.5 when convenient.

Data as of 30 Oct 2026, 20:52 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (EEF)	CVSS 4.0	5.3

Patch: Available – fixed in 4.4.0, 3.3.5

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade phoenixframework phoenix_html to 4.4.0 or 3.3.5.

Affected software

Product	Affected	Fixed in
phoenixframeworkphoenix_html	Affected >=4.0.0 <4.4.0	Fixed in 4.4.0
phoenixframeworkphoenix_html	Affected >=1.0.0 <3.3.5	Fixed in 3.3.5
phoenix_htmlphoenixframework/phoenix_html	Affected ≥ 6ad3a1d7960891a468d54636054a98e11dfb5111, < d9e4e6b2d9be49e25fb6d6b4fdbb2008174f01a6	Fixed in–
Hexphoenix_html`pkg:hex/phoenix_html`Other threats	Affected >=1.0.0 <3.3.5 >=4.0.0 <4.4.0	Fixed in 3.3.5 4.4.0

CPE configurations (1)

cpe:2.3:a:phoenixframework:phoenix_html:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Fixed versions 3.3.5 and 4.4.0 of phoenix_html address this vulnerability. Users should upgrade to phoenix_html version 3.3.5 or later if using the 1.x to 3.x series, or to version 4.4.0 or later if using the 4.x series. No other mitigation or workaround is indicated. Applications should avoid building attribute keys from untrusted input or ensure input is properly sanitized before rendering.

Description

CVE-2026-117645 is a cross-site scripting (XSS) vulnerability in the phoenix_html library of the phoenixframework. It arises from improper neutralization of input during web page generation, specifically in the handling of attribute names in HTML rendering functions. The vulnerability affects phoenix_html versions from 1.0.0 up to but not including 3.3.5, and from 4.0.0 up to but not including 4.4.0. The issue allows an attacker controlling attribute names to inject malicious attributes and scripts into rendered HTML. This occurs because attribute names are not properly escaped, enabling injection via constructs like HEEx <tag {@attrs}>, content_tag/3, or direct calls. Fixed versions are 3.3.5 and 4.4.0.

Impact

An attacker who can control attribute names in HTML rendering can inject arbitrary attributes and scripts into web pages, leading to cross-site scripting (XSS). This can result in execution of malicious scripts in the context of the affected web application, potentially compromising user data or session integrity. The vulnerability requires the attacker to influence attribute keys that are rendered without proper escaping. The CVSS 4.0 score is 5.3 (medium severity), indicating a moderate risk with network attack vector, low complexity, no privileges required, user interaction needed, and low impact on confidentiality and integrity.

CWE-79Improper Neutralization of Input During Web Page Generation (Cross-site Scripting) (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (1)

Description

AI analysisMachine-generated, updated 30 Oct 2026, 20:52 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats