Vulnerability in ethyca-fides (CVE-2026-42303)
Summary
Vulnerability in ethyca-fides (CVE-2026-42303). Risk of unauthorized operations or information disclosure. Exploitable via true. Mitigation: upgrade to 2.83.2 or later.
Original description
The description as published by the source.
Fides is an open-source privacy engineering platform. From 2.75.0 to before 2.83.2, Fides deployments that enable both subject identity verification and duplicate privacy request detection are affected by a vulnerability in which an administrator can approve a privacy request whose identity was never verified. For erasure policies, this can result in unauthorized deletion of a data subject's records across every integration configured in the affected deployment. This vulnerability is fixed in 2.83.2.
Source: NIST National Vulnerability Database 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-42303 has been found in ethyca-fides.
Attackers can target a specific entry point like true over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade ethyca-fides to 2.83.2 or later.
If unsure, ask your IT team or search "ethyca-fides CVE-2026-42303" on the vendor's site.
CVE-2026-42303 (ethyca-fides) — CWE-288
Attack surface: true / subject_identity_verification_required / false / fides.toml
Patched: 2.83.2 — 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.
A vulnerability (CWE-288) exists in ethyca-fides. Attackers reach the vulnerable code path via true.
Check the vendor advisory for the affected versions of ethyca-fides. Attack surface: true / subject_identity_verification_required / false / fides.toml.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.83.2.
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 '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 patch patch
Upgrade ethyca-fides to 2.83.2ステージング環境で 2.83.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-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
- patch github.com
- patch github.com
- patch github.com
- web github.com
- web github.com