{"id":"CVE-2020-25695","year":2020,"sequence":25695,"component":"core server","score":8.8,"cvss_version":"3.0","vector":"AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","first_published":"2020-11-12","source_url":"https://www.postgresql.org/support/security/CVE-2020-25695/","facts":{"affected":{"10":"10","11":"11","12":"12","13":"13","9.5":"9.5","9.6":"9.6"},"component":"core server","cvss_version":"3.0","description_en":"An attacker having permission to create non-temporary objects in at least one schema can execute arbitrary SQL functions under the identity of a superuser.\n\nWhile promptly updating PostgreSQL is the best remediation for most users, a user unable to do that can work around the vulnerability by disabling autovacuum and not manually running ANALYZE , CLUSTER , REINDEX , CREATE INDEX , VACUUM FULL , REFRESH MATERIALIZED VIEW , or a restore from output of the pg_dump command. Performance may degrade quickly under this workaround.\n\nVACUUM without the FULL option is safe, and all commands are fine when a trusted user owns the target object.\n\nThe PostgreSQL project thanks Etienne Stalmans for reporting this problem.","first_published":"2020-11-12","fixed":{"10":"10.15","11":"11.10","12":"12.5","13":"13.1","9.5":"9.5.24","9.6":"9.6.20"},"id":"CVE-2020-25695","introduced":{},"published":{"10":"2020-11-12","11":"2020-11-12","12":"2020-11-12","13":"2020-11-12","9.5":"2020-11-12","9.6":"2020-11-12"},"score":8.8,"title":"Multiple features escape \"security restricted operation\" sandbox","url":"https://www.postgresql.org/support/security/CVE-2020-25695/","vector":"AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"},"reviewed_hash":"6a65a7884245936f6adaef8709d290d460e999dfce1ad78734fa7c9a324ed325","source_hash":"965b9e2323feab543f3cbeb74c418c3a5b43cbefc6594d2862ff0d24dcf8e6a2","text":{"locale":"en","title":"Multiple features escape \"security restricted operation\" sandbox","description":"An attacker having permission to create non-temporary objects in at least one schema can execute arbitrary SQL functions under the identity of a superuser.\n\nWhile promptly updating PostgreSQL is the best remediation for most users, a user unable to do that can work around the vulnerability by disabling autovacuum and not manually running ANALYZE , CLUSTER , REINDEX , CREATE INDEX , VACUUM FULL , REFRESH MATERIALIZED VIEW , or a restore from output of the pg_dump command. Performance may degrade quickly under this workaround.\n\nVACUUM without the FULL option is safe, and all commands are fine when a trusted user owns the target object.\n\nThe PostgreSQL project thanks Etienne Stalmans for reporting this problem.","details":null,"format":"plain","provenance":{"fetched_at":"2026-09-26T10:56:06+00:00","path":"compare/security.json","root":"source-data","sha256":"6a65a7884245936f6adaef8709d290d460e999dfce1ad78734fa7c9a324ed325","source_archive_sha256":"8d8ad63581e1d27b3a0f995ded3feb81c265e38b2ac652eb22f022f52c2240ec","source_revision":"004bc292ee31c11f9a41ab007e9d8116bce29a71","source_url":"https://www.postgresql.org/support/security/"},"text_hash":"420ee52a8bc46c53963698bdfbc44691571274dfc567a17e4a46ff9af386cd65"},"locales":["en"],"fixes":[{"major":"10","fixed_version":"10.15","introduced":null,"published_date":"2020-11-12","facts":{"fixed":"10.15","introduced":null,"published":"2020-11-12"}},{"major":"11","fixed_version":"11.10","introduced":null,"published_date":"2020-11-12","facts":{"fixed":"11.10","introduced":null,"published":"2020-11-12"}},{"major":"12","fixed_version":"12.5","introduced":null,"published_date":"2020-11-12","facts":{"fixed":"12.5","introduced":null,"published":"2020-11-12"}},{"major":"13","fixed_version":"13.1","introduced":null,"published_date":"2020-11-12","facts":{"fixed":"13.1","introduced":null,"published":"2020-11-12"}},{"major":"9.5","fixed_version":"9.5.24","introduced":null,"published_date":"2020-11-12","facts":{"fixed":"9.5.24","introduced":null,"published":"2020-11-12"}},{"major":"9.6","fixed_version":"9.6.20","introduced":null,"published_date":"2020-11-12","facts":{"fixed":"9.6.20","introduced":null,"published":"2020-11-12"}}],"legacy":[]}