# Apache AGE: Python and Golang drivers allow data manipulation and exposure due to SQL injection

Advisory record · `GHSA-6p5q-h963-pwwf`

- **Identifiers:** `GHSA-6p5q-h963-pwwf` · `CVE-2022-45786` · `GO-2024-2587` · `PYSEC-2026-769`
- **State:** Confirmed
- **Severity:** CVSS 8.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-89](https://cwe.mitre.org/data/definitions/89.html)
- **Tags:** [SQL injection](https://agentprime.io/advisories/tag/sql-injection.md)
- **Published:** 4 Feb 2023
- **Updated:** 7 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 4 Feb 2023, 21:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/apache/age/drivers/golang` (Go): affected `<1.1.1`; fixed in `1.1.1`
- `apache-age-python` (PyPI): affected `<0.0.5`; fixed in `0.0.5`

## Machine-written summary

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

> Apache AGE's Golang driver (github.com/apache/age/drivers/golang) before 1.1.1 and its Python driver (apache-age-python) before 0.0.5 are vulnerable to SQL injection, affecting AGE for PostgreSQL 11 and 12 through version 1.1.0 when those drivers are used. An attacker who can supply input to queries built by the drivers could manipulate data or read exposed data. The source gives few details on the exact attack conditions. Upgrade the Golang driver to 1.1.1 or later and the Python driver to 0.0.5 or later, and also update AGE to the latest version for PostgreSQL 11 or 12.

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.0100, the 63rd percentile, on 22 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:06 UTC: First seen by agentprime
- 31 Oct 2026, 15:06 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6p5q-h963-pwwf)

## Sources

- [GitHub Advisory Database: GHSA-6p5q-h963-pwwf](https://github.com/advisories/GHSA-6p5q-h963-pwwf)
- [OSV: GHSA-6p5q-h963-pwwf](https://osv.dev/vulnerability/GHSA-6p5q-h963-pwwf)
- <https://nvd.nist.gov/vuln/detail/CVE-2022-45786>
- <https://github.com/apache/age>
- <https://lists.apache.org/thread/of8x0gt5d2vfrm5ksxw55bwn2849ck1w>

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

---

The web page: <https://agentprime.io/advisories/GHSA-6p5q-h963-pwwf/>. Everything for agents: <https://agentprime.io/llms.txt>.
