PatchTheCVECVE-2025-0218: When batch jobs are executed by pgAgent, a script is created in a temporary directory and then executed
CVE-2025-0218 is a medium-severity flaw (CVSS 5.5) affecting pgagent. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- No elevated risk signals yet
A fixed release or distro patch exists.
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2025-0218?
pgagent: upgrade to 4.2.3. Exact commands for each OS are on this page.
Is CVE-2025-0218 being exploited?
CVE-2025-0218 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2025-0218 affect?
CVE-2025-0218 affects pgagent. Severity is medium (CVSS 5.5). 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, lea
How urgent is CVE-2025-0218?
Priority 21/100. No elevated risk signals yet.