Skip to content
Sign in
CVE-2020-25696Not scoredCWE-183

CVE-2020-25696: PostgreSQL vulnerability

Postgresql · PostgreSQL

Vendor fix available · Affected: PostgreSQL · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

2.7%probability of exploitation in the next 30 days
86th percentile
050100

Higher than 86% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

A flaw was found in the psql interactive terminal of PostgreSQL in versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24. If an interactive psql session uses \gset when querying a compromised server, the attacker can execute arbitrary code as the operating system account running psql. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • PostgreSQLAll PostgreSQL versions before 13.1, before 12.5, before 11…

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV
Not listed
Public check
No public nuclei template
Published
November 2020

CoverageNo articles yet

No CyberSIXT article names CVE-2020-25696 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

Updated AboutDevelopersSign in