# CVE-2025-0218: Race condition in pgAgent

> A local attacker can prevent pgAgent from executing scheduled jobs by pre-creating predictable temporary directories, causing a denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jan 2025
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2025-0218, DLA-4338-1, GHSA-j2pc-4j53-q3ww, UBUNTU-CVE-2025-0218

## What is CVE-2025-0218?

CVE-2025-0218 is a medium-severity vulnerability in pgAgent, published on 7 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

When batch jobs are executed by pgAgent, a script is created in a temporary directory and then executed. In versions of pgAgent prior to 4.2.3, an insufficiently seeded random number generator is used when generating the directory name, leading to the possibility for a local attacker to pre-create the directory and thus prevent pgAgent from executing jobs, disrupting scheduled tasks.

Weakness: CWE-330 (Use of Insufficiently Random Values), CWE-340 (Generation of Predictable Numbers or Identifiers)

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

It affects 1 product.


Products: Pgadmin Pgagent.

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

Upgrade to a fixed version.

## Is CVE-2025-0218 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0218 is a medium-severity vulnerability in pgAgent, published on 7 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0218 in the wild and no public exploit code.

Affected product: pgAgent. 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-0218/ (Markdown: https://insights.sbomify.com/CVE-2025-0218/index.md)
```

## Sources

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

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