Is CVE-2026-122079 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-122079 being exploited in the wild.

How severe is CVE-2026-122079?

Informational severity, published 4 November 2026.

Which products and versions are affected?

Drupal htmLawed 4.1.0 to 4.1.10; Packagist:Https://Packages.Drupal.Org/8 Drupal/Htmlawed ECOSYSTEM:introduced=4.1.0,fixed=4.1.11.

How is CVE-2026-122079 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-122079?

Check whether you run Drupal htmLawed or Packagist:Https://Packages.Drupal.Org/8 Drupal/Htmlawed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-122079: Drupal htmLawed module cross-site scripting in attribute filtering

CVE-2026-122079 · Severity: info · Published 2026-11-04

The htmLawed module for Drupal is a content filter that restricts and sanitizes HTML input in text fields. Due to insufficient attribute filtering, attackers can inject malicious scripts that execute in users' browsers when the filtered content is displayed, potentially compromising user accounts and sensitive data. This affects Drupal installations with core version greater than 11.2 or any version containing the HTMX library.

Vendors: Drupal, Packagist:Https://Packages.Drupal.Org/8.

Quick answers

Is CVE-2026-122079 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-122079 being exploited in the wild.
How severe is CVE-2026-122079?: Informational severity, published 4 November 2026.
Which products and versions are affected?: Drupal htmLawed 4.1.0 to 4.1.10; Packagist:Https://Packages.Drupal.Org/8 Drupal/Htmlawed ECOSYSTEM:introduced=4.1.0,fixed=4.1.11.
Is there a fix for CVE-2026-122079?: Yes. Packagist:Https://Packages.Drupal.Org/8 Drupal/Htmlawed: upgrade to 4.1.11 or later. Until then: For Text Formats using the htmLawed filter, update the filter configuration's deny_attribute parameter to include 'data-hx-*' to block HTMX attributes. Example: 'deny_attribute'=>'data-hx-*, id, style'. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-122079 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-122079?: Check whether you run Drupal htmLawed or Packagist:Https://Packages.Drupal.Org/8 Drupal/Htmlawed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Packagist:Https://Packages.Drupal.Org/8 Drupal/Htmlawed: upgrade to 4.1.11 or later

For Text Formats using the htmLawed filter, update the filter configuration's deny_attribute parameter to include 'data-hx-*' to block HTMX attributes. Example: 'deny_attribute'=>'data-hx-*, id, style'.

Technical details

The htmLawed filter fails to adequately strip dangerous HTML attributes, allowing cross-site scripting attacks through insufficiently blocked data-hx-* attributes (HTMX library directives). The vulnerability affects versions 4.1.0 through 4.1.10; exploitation requires user interaction to view maliciously crafted content in an affected Text Format. A fix is available in version 4.1.11, and mitigation involves configuring the filter's deny_attribute parameter to explicitly block data-hx-* attributes.

Affected products

Drupal htmLawed 4.1.0 to 4.1.10

Identifiers

CVE-2026-122079
DRUPAL-CONTRIB-2026-315

Timeline

2026-11-04: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.