Cross-Site Scripting (XSS) in actionview (CVE-2026-33168)
Summary
Cross-site scripting in actionview (CVE-2026-33168). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 7.2.3.1 or later.
Original description
The description as published by the source.
Impact
When a blank string is used as an HTML attribute name in Action View tag helpers, the attribute escaping is bypassed, producing malformed HTML. 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 attributes are affected.
Releases
The fixed releases are available at the normal locations.
Credit
This issue was responsibly reported by Hackerone researcher taise.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-33168 has been found in actionview.
Risk of unauthorized operations or information disclosure.
What to do: upgrade actionview to 7.2.3.1 or later.
If unsure, ask your IT team or search "actionview CVE-2026-33168" on the vendor's site.
CVE-2026-33168 (actionview) — CWE-79
Patched: 7.2.3.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in actionview.
Check the vendor advisory for the affected versions of actionview.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 7.2.3.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'actionview' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'actionview' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
actionviewを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade actionview to 7.2.3.1ステージング環境で 7.2.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-33168 rails
- Ubuntu UBUNTU-CVE-2026-33168 rails
References
- advisory nvd.nist.gov
- DSA DSA-6546-1
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com