Skip to content
Threat Brief

← All advisories

CVE-2026-126069

Medium 4.7No known exploitationFix available

Action View: Possible XSS vulnerability in Action View tag helpers

Vendor advisory: GHSA-68p9-83h6-5wpj

Record last updated

CVSS score

4.7

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

Higher than 15% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

Action View is a framework for handling view template lookup and rendering and provides view helpers for building HTML. Prior to 8.1.4.1 and 8.0.5.2, the fix for CVE-2026-33168 skips blank HTML attribute names in Action View tag helpers, but it tests the name before converting it to a string. A Symbol name made only of whitespace, such as :" ", is not blank, because Symbol#blank? is Symbol#empty?, so it reaches the attribute escaping, which emits an attribute with no name and produces malformed HTML. The asset tag helpers, such as image_tag, video_tag and audio_tag, symbolize their options, so a whitespace String name passed to them takes the same path. A carefully crafted attribute value could then be misinterpreted by the browser as a separate attribute name, possibly leading to XSS. Applications that allow users to specify custom HTML attribute names are affected. This issue is fixed in versions 8.1.4.1 and 8.0.5.2.

Weakness: CWE-79

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
Microsoftazl4 rubygem-actionview 8.0.2-5.azl4 on Azure Linux 4.0Not documentedNot documentedMicrosoft MSRC
rubygemsactionviewfrom 8.1.0.beta1 before 8.1.4.18.1.4.1GitHub Advisory Database
rubygemsactionviewall versions before 8.0.5.28.0.5.2GitHub Advisory Database

Timeline

  1. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  2. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references