https://www.postgresql.org/support/security/CVE-2025-1094/ https://www.postgresql.org/support/security/CVE-2025-1094/ > Improper neutralization of quoting synt

https://www.postgresql.org/support/security/CVE-2025-1094/ https://www.postgresql.org/support/security/CVE-2025-1094/ > Improper neutralization of quoting syntax in PostgreSQL libpq functions PQescapeLiteral(), PQescapeIdentifier(), PQescapeString(), and PQescapeStringConn() allows a database input provider to achieve SQL injection in certain usage patterns. Specifically, SQL injection requires the application to use the function result to construct input to psql, the PostgreSQL interactive terminal. Wait, what kind of system design uses programmatic input to psql, the command-line tool? Are they like shelling out to psql, instead of using a SQL client library? > Similarly, improper neutralization of quoting syntax in PostgreSQL command line utility programs allows a source of command line arguments to achieve SQL injection when client_encoding is BIG5 and server_encoding is one of EUC_TW or MULE_INTERNA BIG5 is Chinese encoding, so I'm assuming the actual attack was the other route.