# SSRF vulnerability using the Aegis DataBinding in Apache CXF

Advisory record · `GHSA-qmgx-j96g-4428`

- **Identifiers:** `GHSA-qmgx-j96g-4428` · `CVE-2024-28752`
- **State:** Confirmed
- **Severity:** CVSS 9.3 Critical
- **Critical:** Yes: CVSS 9+
- **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:** 15 Mar 2024
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 15 Mar 2024, 12:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.3: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `org.apache.cxf:cxf-rt-databinding-aegis` (Maven): affected `<3.5.8 || >=3.6.0, <3.6.3 || >=4.0.0, <4.0.4`; fixed in `3.5.8`, `3.6.3`, `4.0.4`

## Machine-written summary

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

> Apache CXF's cxf-rt-databinding-aegis package is vulnerable in versions before 3.5.8, from 3.6.0 before 3.6.3, and from 4.0.0 before 4.0.4. An attacker who can send requests to a web service that uses the Aegis data binding and takes at least one parameter can perform server-side request forgery. Users of other data bindings, including the default one, are not affected. Upgrade to 3.5.8, 3.6.3, or 4.0.4, depending on your release line.

Written 2 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

- 9.3 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N`, from GitHub Advisory Database

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

## Timeline

- 31 Oct 2026, 14:18 UTC: First seen by agentprime
- 31 Oct 2026, 14:18 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-qmgx-j96g-4428)

## Sources

- [GitHub Advisory Database: GHSA-qmgx-j96g-4428](https://github.com/advisories/GHSA-qmgx-j96g-4428)
- [OSV: GHSA-qmgx-j96g-4428](https://osv.dev/vulnerability/GHSA-qmgx-j96g-4428)
- <https://nvd.nist.gov/vuln/detail/CVE-2024-28752>
- <https://github.com/apache/cxf/commit/d0baeb3ee64c6d7c883bd2f5c4cb0de6b0b5f463>
- <https://cxf.apache.org/security-advisories.data/CVE-2024-28752.txt>
- <https://github.com/apache/cxf>
- <https://security.netapp.com/advisory/ntap-20240517-0001>
- <http://www.openwall.com/lists/oss-security/2024/03/14/3>

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-qmgx-j96g-4428>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-qmgx-j96g-4428/>. Everything for agents: <https://agentprime.io/llms.txt>.