Skip to main content
VulnerabilityPublished

CVE-2026-126741: Smart trim · This module implements a field formatter for text fields that improves the Summary or

Affects drupal/smart_trimSource GCVE Database

0
Compare

Not known to be exploited : upgrade to 2.3.2 or 2.2.2 when convenient.

Data as of 11 Nov 2026, 20:17 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch
Available – fixed in 2.3.2, 2.2.2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 11 Nov 2026.

What to do

Upgrade drupal/smart_trim to 2.3.2 or 2.2.2.

Affected software

ProductAffectedFixed in
Packagist https //packages.drupal.org/8drupal/smart_trimAffected
  • <2.2.2
  • >=2.3.0 <2.3.2
Fixed in
  • 2.2.2
  • 2.3.2

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

AI-suggested

Upgrade to smart_trim module versions 2.2.2 or 2.3.2 or later, which contain fixes for this vulnerability. If the site uses only the field formatter without the Twig filter, no action is required.

Description

The Drupal smart_trim module contains a vulnerability where unsafe HTML is not sufficiently escaped when processed through its Twig filter, potentially allowing content injection. This issue requires an attacker to have a role capable of posting content that is rendered using the module's Twig filters. Sites using only the field formatter without the Twig filter are not vulnerable. Fixed versions 2.2.2 and 2.3.2 address this issue.

References

Community reviews

Loading reviews…