Pgadmin Pgagent
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Pgadmin Pgagent.
By the Year
In 2025 there have been 1 vulnerability in Pgadmin Pgagent with an average score of 7.1 out of ten. Pgagent did not have any published security vulnerabilities last year. That is, 1 more vulnerability have already been reported in 2025 as compared to last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2025 | 1 | 7.10 |
| 2024 | 0 | 0.00 |
| 2023 | 0 | 0.00 |
| 2022 | 0 | 0.00 |
| 2021 | 0 | 0.00 |
| 2020 | 0 | 0.00 |
| 2019 | 0 | 0.00 |
| 2018 | 0 | 0.00 |
It may take a day or so for new Pgagent vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Pgadmin Pgagent Security Vulnerabilities
When batch jobs are executed by pgAgent, a script is created in a temporary directory and then executed
CVE-2025-0218
7.1 - High
- January 07, 2025
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.
Use of Insufficiently Random Values
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Pgadmin Pgagent or by Pgadmin? Click the Watch button to subscribe.
