PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-107264 drupal CVE debrief

The Inline Formatter Field module for Drupal allows site builders to template and style entities with a field but does not properly protect against template injection when parsing. This vulnerability may allow users to render protected data or execute unsafe Twig commands. Site administrators and security teams should assess exposure and prioritize patching to prevent potential data access or command execution. The vulnerability is related to template injection in the Inline Formatter Field module, which could lead to unauthorized data access or execution of unsafe Twig commands by users with entity creation or editing capabilities.

Vendor
drupal
Product
inline_formatter_field
CVSS
Unknown
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-07
Original CVE updated
2026-10-07
Advisory published
2026-10-07
Advisory updated
2026-10-07

Who should care

Drupal site administrators, security teams, and developers who use the Inline Formatter Field module should assess exposure and take necessary actions. Site administrators should verify exposure, prioritize patching, and restrict Twig commands to prevent potential data access or command execution. Security teams should review and restrict Twig commands and data access for users who can create or edit entities with fields using the Inline Formatter Field.

Why it matters

CVE-2026-107264 is a template injection vulnerability in the Inline Formatter Field module for Drupal. Site administrators and security teams should verify exposure, prioritize patching, and restrict Twig commands to prevent potential data access or command execution.

  • Potential unauthorized data access or exposure through rendered protected data.
  • Possible execution of unsafe Twig commands by users with entity creation or editing capabilities.
  • Need for verification of Inline Formatter Field module version and exposure.
  • Prioritization of patching or mitigating the vulnerability to prevent potential exploitation.

Technical summary

The Inline Formatter Field module for Drupal does not properly protect against template injection when parsing, potentially allowing users to render protected data or execute unsafe Twig commands. The vulnerability is related to template injection in the Inline Formatter Field module, which could lead to unauthorized data access or execution of unsafe Twig commands by users with entity creation or editing capabilities. Site administrators and security teams should assess exposure and prioritize patching to prevent potential data access or command execution.

Defensive priority

Drupal site administrators and security teams should prioritize verifying exposure and applying patches or mitigations.

Recommended defensive actions

  • Verify if the Inline Formatter Field module is installed and enabled on your Drupal site.
  • Check the version of the Inline Formatter Field module and update to version 4.2.0 or later if necessary.
  • Review and restrict Twig commands and data access for users who can create or edit entities with fields using the Inline Formatter Field module.
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.

Evidence notes

The vulnerability is described in the source item from osv_dev and is related to the Inline Formatter Field module for Drupal. The CVE Program and NVD provide additional context. The Inline Formatter Field module does not properly protect against template injection when parsing, potentially allowing users to render protected data or execute unsafe Twig commands. The vulnerability may allow users to render protected data or execute unsafe Twig commands. The CVE record was published on 2026-10-07T16:27:03.000Z and has not been modified.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-107264 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-107264

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-107264 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-107264

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • DRUPAL-CONTRIB-2026-203

    Unverified legacy reference

    URL: https://storage.googleapis.com/osv-vulnerabilities/Packagist/DRUPAL-CONTRIB-2026-203.json

    osv_dev

  • Source reference

    Unverified legacy reference

    URL: https://www.drupal.org/sa-contrib-2026-203

    Supplemental source

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.