# CVE-2025-52467: pgai secrets exfiltration via `pull_request_target`

> Attackers can exfiltrate GitHub secrets and gain write access to the repository via a pull_request_target workflow vulnerability in the pgai library.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2025
- **Updated:** 23 Jun 2025
- **Also known as:** GHSA-89qq-hgvp-x37m

## What is CVE-2025-52467?

CVE-2025-52467 is a critical vulnerability in timescale pgai, published on 19 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

pgai is a Python library that transforms PostgreSQL into a retrieval engine for RAG and Agentic applications. Prior to commit 8eb3567, the pgai repository was vulnerable to an attack allowing the exfiltration of all secrets used in one workflow. In particular, the GITHUB_TOKEN with write permissions for the repository, allowing an attacker to tamper with all aspects of the repository, including pushing arbitrary code and releases. This issue has been patched in commit 8eb3567.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-52467?


## How do I fix CVE-2025-52467?

No fix has been published for CVE-2025-52467 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-52467 being exploited?

There is no known exploitation of CVE-2025-52467 in the wild and no public exploit code.

Public exploit code:

- Security research lab: reproduction of CVE-2025-52467 (pgai pull_request_target workflow code execution / GITHUB_TOKEN exfiltration) — snapshot of timescale/pgai (github_poc): https://github.com/pvharmo2/gha-lab-e8902eccd3

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-52467 and fix it if it is affected.

What it is: CVE-2025-52467 is a critical vulnerability in timescale pgai, published on 19 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-52467 in the wild and no public exploit code.

Affected product: timescale pgai. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-52467/ (Markdown: https://insights.sbomify.com/CVE-2025-52467/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-52467
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-52467
- OSV: https://osv.dev/vulnerability/CVE-2025-52467

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-52467/
Summaries are generated and may contain mistakes; the official description above is the record.