CVE-2025-0218 is a vulnerability in pgAgent, a job scheduling agent for PostgreSQL, affecting versions prior to 4.2.3. The issue arises from the use of an insufficiently seeded random number generator when creating temporary directories for batch job scripts. When pgAgent executes a scheduled job, it generates a directory name in a temporary location to store the script before execution. Because the random number generator is predictable, a local attacker with low privileges can anticipate the directory name and pre-create it. This pre-creation causes pgAgent to fail in creating the directory and thus prevents the execution of scheduled jobs. The vulnerability impacts availability by disrupting automated batch jobs but does not affect confidentiality or integrity of data. Exploitation requires local access with low privileges but no user interaction. The CVSS 3.1 score is 5.5, reflecting medium severity due to the limited attack vector and impact confined to availability. No known exploits are currently reported in the wild. The vulnerability was published on January 7, 2025, and the fix is available in pgAgent version 4.2.3 and later. Organizations using pgAgent for PostgreSQL job scheduling should prioritize patching to ensure reliable task execution.

For European organizations, this vulnerability primarily threatens the availability of automated batch jobs managed by pgAgent. Disruption of scheduled tasks can affect database maintenance, backups, data processing pipelines, and other critical automated workflows. This can lead to operational delays, increased manual intervention, and potential compliance issues if scheduled jobs are part of regulatory reporting or data retention processes. While the vulnerability does not expose sensitive data or allow unauthorized data modification, the interruption of services can degrade business continuity and impact dependent applications. Organizations with complex PostgreSQL environments relying heavily on pgAgent for automation are at higher risk. The requirement for local access limits remote exploitation, but insider threats or compromised internal accounts could leverage this vulnerability. The medium severity rating indicates a moderate risk that should be addressed promptly to maintain operational stability.

The primary mitigation is to upgrade pgAgent to version 4.2.3 or later, where the random number generator seeding issue has been resolved. Until patching is possible, organizations should restrict local user permissions to prevent unauthorized users from creating directories in the temporary locations used by pgAgent. Implement strict access controls and monitoring on systems running pgAgent to detect suspicious directory creation attempts. Consider isolating pgAgent execution environments to minimize the number of users with local access. Regularly audit scheduled job execution logs to identify failures potentially caused by this vulnerability. Additionally, review and harden the system's temporary directory permissions and consider using filesystem-level protections such as mandatory access controls (e.g., SELinux, AppArmor) to prevent unauthorized directory manipulation. Incorporating these measures will reduce the risk of exploitation and maintain job scheduling reliability.