CVE-2025-0218: When batch jobs are executed by pgAgent, a script is created in a temporary directory and then executed
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium : upgrade to 4.2.3 when convenient.
Data as of 29 Oct 2026, 23:52 UTC
Thin evidence
One scorer or none| CNA (PostgreSQL) | CVSS 3.1 | 5.5 |
|---|
- Patch
- Available – fixed in 4.2.3
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 7 Jan 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade pgadmin-org/pgagent to 4.2.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubpgadmin-org/pgagentpkg:github/pgadmin-org/pgagentOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade pgAgent to version 4.2.3 or later, where the random number generator for temporary directory names is properly seeded. No other mitigation is indicated.
Description
pgAgent versions prior to 4.2.3 use an insufficiently seeded random number generator to create temporary directory names for batch job scripts. This allows a local attacker to pre-create the directory, preventing pgAgent from executing scheduled jobs and causing disruption.