Skip to main content
Mallory
UnratedVulnerability

CVE-2026-122080: Cross-site scripting in Drupal htmLawed via malformed UTF-8

Updated 17 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-122080CWE-79

A cross-site scripting vulnerability in the Drupal htmLawed module allows malformed UTF-8 characters to bypass malicious HTML filtering. The vulnerability affects only sites using an SQLite database and an htmLawed library version earlier than 1.2.17. Successful exploitation allows attacker-controlled scripts to execute in users' browser sessions.

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.

Attackers can bypass HTML sanitization and execute malicious scripts in users' browser sessions, potentially compromising the confidentiality and integrity of site data accessible to those users. The vulnerability is rated moderately critical, with a risk score of 11/25, complex attack conditions, and user-level access required.

Mitigation

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

Updating the bundled htmLawed library to version 1.2.17 or later is an alternative to upgrading the module. No separate temporary workaround is specified.

Remediation

Patch, then assume compromise.

Upgrade the Drupal htmLawed module's 4.1.x branch to 4.1.11 or the 8.x-3.x branch to 8.x-3.10. Fixes were first introduced in versions 4.1.8 and 8.x-3.9, respectively. Alternatively, replace the bundled htmLawed library with version 1.2.17 or later.

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-122080 exploited in the wild?
As of Nov 4, 2026, Mallory has no reports of CVE-2026-122080 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-122080?
As of Nov 4, 2026, Mallory has found no public exploit for CVE-2026-122080.
Is there a patch for CVE-2026-122080?
Upgrade the Drupal htmLawed module's 4.1.x branch to 4.1.11 or the 8.x-3.x branch to 8.x-3.10. Fixes were first introduced in versions 4.1.8 and 8.x-3.9, respectively.
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.