# Apache Jena vulnerable to Deserialization of Untrusted Data

Advisory record · `GHSA-g2qw-6vrr-v6pq`

- **Identifiers:** `GHSA-g2qw-6vrr-v6pq` · `CVE-2022-45136`
- **State:** Confirmed
- **Severity:** CVSS 9.8 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-502](https://cwe.mitre.org/data/definitions/502.html)
- **Tags:** [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md)
- **Published:** 14 Nov 2022
- **Updated:** 2 Aug 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 Nov 2022, 19:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.8: 9.0 or more.

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

## Affected packages

- `org.apache.jena:jena-sdb` (Maven): affected `<=3.17.0`; no fixed version yet

## Machine-written summary

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

> Apache Jena SDB (jena-sdb) versions 3.17.0 and earlier are vulnerable to a JDBC deserialization attack if an attacker can control the JDBC URL or cause the database server to return malicious data. The source says the MySQL JDBC driver is known to be affected by this class of attack, and an application using Apache Jena SDB could then allow remote code execution when connected to a malicious database server. No fixed version is listed; the project has been end-of-life since December 2020, and the source recommends migrating to an alternative such as Apache Jena TDB 2.

Written 8 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.8 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from GitHub Advisory Database

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

## Timeline

- 31 Oct 2026, 15:13 UTC: First seen by agentprime
- 31 Oct 2026, 15:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-g2qw-6vrr-v6pq)

## Sources

- [GitHub Advisory Database: GHSA-g2qw-6vrr-v6pq](https://github.com/advisories/GHSA-g2qw-6vrr-v6pq)
- [OSV: GHSA-g2qw-6vrr-v6pq](https://osv.dev/vulnerability/GHSA-g2qw-6vrr-v6pq)
- <https://nvd.nist.gov/vuln/detail/CVE-2022-45136>
- <https://github.com/apache/jena>
- <https://lists.apache.org/thread/mc77cdl5stgjtjoldk467gdf756qjt31>
- <http://www.openwall.com/lists/oss-security/2022/11/14/5>

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-g2qw-6vrr-v6pq>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-g2qw-6vrr-v6pq/>. Everything for agents: <https://agentprime.io/llms.txt>.
