Skip to main content
Mallory
UnratedVulnerability

CVE-2026-122079: Cross-site scripting in Drupal htmLawed HTML attribute filtering

Updated 18 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-122079CWE-79

CVE-2026-122079 is a cross-site scripting vulnerability in the Drupal htmLawed module caused by insufficient HTML attribute filtering. Versions 4.1.0 through 4.1.10 are affected on sites running Drupal core newer than 11.2, or any Drupal core version with the HTMX library. Failure to deny HTMX-related data-hx-* attributes allows attacker-controlled HTML to bypass filtering and execute script in users' browsers. The 8.x-3.x branch is not affected.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can execute attacker-controlled script in users' browser sessions, compromising confidentiality and integrity within the affected site's security context. The vulnerability is rated moderately critical at 14/25, with basic attack complexity and a user-level access requirement.

Mitigation

If you can’t patch tonight, do this now.

For every Text Format using the htmLawed filter, add data-hx-* to the filter configuration's deny_attribute parameter, preserving any existing attribute restrictions.

Remediation

Patch, then assume compromise.

Upgrade affected htmLawed 4.1.x installations to version 4.1.11 or a later fixed release. Review every Text Format using the htmLawed filter and update its configuration to deny data-hx-* attributes. The 8.x-3.x branch does not require an update for this vulnerability.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-122079 exploited in the wild?
As of Nov 4, 2026, Mallory has no reports of CVE-2026-122079 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-122079?
As of Nov 4, 2026, Mallory has found no public exploit for CVE-2026-122079.
Is there a patch for CVE-2026-122079?
Upgrade affected htmLawed 4.1.x installations to version 4.1.11 or a later fixed release. Review every Text Format using the htmLawed filter and update its configuration to deny data-hx-* attributes.
Activity feed

Recent activity

1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.