Cross-Site Scripting (XSS) in ethyca-fides (CVE-2026-44541)
Summary
Cross-site scripting in ethyca-fides (CVE-2026-44541). Risk of unauthorized operations or information disclosure. Exploitable via fides.js. Mitigation: upgrade to 2.84.5 or later.
Original description
The description as published by the source.
Fides is an open-source privacy engineering platform. From version 2.33.0 to before version 2.84.5, there is a DOM-based XSS vulnerability in fides.js via the fides_description override. This issue has been patched in version 2.84.5.
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-44541 has been found in ethyca-fides.
Attackers can target a specific entry point like fides.js over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade ethyca-fides to 2.84.5 or later.
If unsure, ask your IT team or search "ethyca-fides CVE-2026-44541" on the vendor's site.
CVE-2026-44541 (ethyca-fides) — CWE-79
Attack surface: fides.js / true / allowHTMLDescription / nh3
Patched: 2.84.5 — apply immediately
Workaround: Set FIDES_PRIVACY_CENTER__ALLOW_HTML_DESCRIPTION=false on the Privacy Center container(s) and redeploy.
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 ethyca-fides. Attackers reach the vulnerable code path via fides.js.
Check the vendor advisory for the affected versions of ethyca-fides. Attack surface: fides.js / true / allowHTMLDescription / nh3.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.84.5.
Workaround: Set FIDES_PRIVACY_CENTER__ALLOW_HTML_DESCRIPTION=false on the Privacy Center container(s) and redeploy.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'ethyca-fides' . 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 'ethyca-fides' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
ethyca-fidesを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Set `FIDES_PRIVACY_CENTER__ALLOW_HTML_DESCRIPTION=false` on the Privacy Center container(s) and redeploy.パッチが適用されるまでの応急処置として、Set
FIDES_PRIVACY_CENTER__ALLOW_HTML_DESCRIPTION=falseon the Privacy Center container(s) and redeploy. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade ethyca-fides to 2.84.5ステージング環境で 2.84.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com
- web github.com