# Fides Server-Side Request Forgery Vulnerability in Custom Integration Upload

Advisory record · `GHSA-jq3w-9mgf-43m4`

- **Identifiers:** `GHSA-jq3w-9mgf-43m4` · `CVE-2023-46124` · `PYSEC-2026-1344`
- **State:** Confirmed
- **Severity:** CVSS 8.2 High
- **Critical:** No
- **Weakness (CWE):** [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md)
- **Published:** 24 Oct 2023
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 24 Oct 2023, 02:14 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `ethyca-fides` (PyPI): affected `<2.22.1`; fixed in `2.22.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Fides (ethyca-fides) versions before 2.22.1 are vulnerable to server-side request forgery through custom integration uploads. An attacker who holds the CONNECTOR_TEMPLATE_REGISTER API scope, which in the Admin UI is limited to root users and owners, can upload specially crafted YAML dataset and config files in a ZIP to make requests to internal systems, including localhost, and exfiltrate data. Upgrade to ethyca-fides 2.22.1 or later. No workaround is listed.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.2 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:L`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0084, the 58th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:36 UTC: First seen by agentprime
- 31 Oct 2026, 14:36 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jq3w-9mgf-43m4)

## Sources

- [GitHub Advisory Database: GHSA-jq3w-9mgf-43m4](https://github.com/advisories/GHSA-jq3w-9mgf-43m4)
- [OSV: GHSA-jq3w-9mgf-43m4](https://osv.dev/vulnerability/GHSA-jq3w-9mgf-43m4)
- <https://github.com/ethyca/fides/security/advisories/GHSA-jq3w-9mgf-43m4>
- <https://nvd.nist.gov/vuln/detail/CVE-2023-46124>
- <https://github.com/ethyca/fides/commit/cd344d016b1441662a61d0759e7913e8228ed1ee>
- <https://github.com/ethyca/fides>
- <https://github.com/ethyca/fides/releases/tag/2.22.1>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-jq3w-9mgf-43m4>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jq3w-9mgf-43m4/>. Everything for agents: <https://agentprime.io/llms.txt>.
