News for hackers. Stuff that matters.
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution by logophobia on Thursday November 12, 2026 @04:14PM (#50474380)
Correct me if I'm wrong, but those all look like sql exploits. Don't those already require some sort of authenticated remote access. They are security issues, but calling them remote code exploitation make them seem more dangerous than they are.

These seem more like privilege escalation, you have access through a database account and use that to gain full access to the whole server. So an issue for multi-tenant databases mostly.

Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution by knorker on Thursday November 12, 2026 @04:19PM (#50474440)
It's RCE even if it's not pre-auth.
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution by vfosnar on Thursday November 12, 2026 @04:26PM (#50474528)
ppl host open Postgres instances, one I can think of is https://postpass.geofabrik.de/ where you can query OpenStreetMap data in a Postgres instance exposed over plain HTTP API
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution by veqq on Thursday November 12, 2026 @05:55PM (#50475587)
Wow, that is... I would have never believed in such a thing.
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution by kccqzy on Thursday November 12, 2026 @05:10PM (#50475045)
You can do authentication and authorization inside sql. For example you could have something like

    CREATE ROLE initial LOGIN NOINHERIT NOCREATEDB NOCREATEROLE NOSUPERUSER;
And then you run SQL to validate any credentials and then check the database for any permissions, ending with

    SET LOCAL ROLE someuser;
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution by mistrial9 on Thursday November 12, 2026 @05:39PM (#50475421)
that requires additional privelages plus login.. I agree with the pp, sensationalism
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution by NooneAtAll5 on Thursday November 12, 2026 @09:07PM (#50477179)
who's pp?
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution by 14u2c on Thursday November 12, 2026 @10:32PM (#50477880)
priginal poster.
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution by paustint on Thursday November 12, 2026 @11:30PM (#50478348)
What's that?
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution by TeMPOraL on Friday November 13, 2026 @04:36AM (#50480753)
It's like original o[y]ster, but with a shift left.
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution by somat on Thursday November 12, 2026 @08:48PM (#50477054)
As an interesting thought experiment, if you do something like this and give your end users a full sql connection almost by definition you can't have a sql injection vulnerability, the database itself limits what access the clients have.

Now as to if this is actually a good idea and the database internal security is robust enough to handle full access, Well I have my doubts, It is a complicated poorly tested interface and results as disclosed by the article in question are probably not surprising.

I do run a toy application, where the experiment was to see if I could push all authentication and access control into the database, It is actually sort of neat not needing an auth layer in the application, but attacks like this were half expected.

see also: the schemaverse. A multiplayer space game where the game engine is postgres. https://github.com/Abstrct/Schemaverse

Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution by dprkh on Thursday November 12, 2026 @11:31PM (#50478354)
Why use SQL for authentication and authorization? I understand that the point of SQL is so that the query optimizer can create an efficient execution plan, but there is no need for that when it comes to configuring auth, right?
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution by simcop2387 on Thursday November 12, 2026 @11:42PM (#50478445)
It can severely simplify a lot of patterns like row level security and other things inside the database that need tigher access controls.
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution by jamesfinlayson on Friday November 13, 2026 @01:02AM (#50478962)
I think at my day job it's used so that a bunch of things can connect to the production database to siphon off data for BI/do ancillary tasks (owned by other teams) without messing anything up, while the main business application that actually writes to the database has the ability to do pretty much everything.
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution by MattPalmer1086 on Friday November 13, 2026 @05:15AM (#50481162)
This is a remote code execution attack - but authenticated, rather than unauthenticated.

Remote does not mean unauthenticated, it means "not local" - as in, over the network.

Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution by wffurr on Friday November 13, 2026 @06:30AM (#50482009)
So it's a little worse than a "it rather involved being on the other side of the airtight hatchway" "bug"; instead it's a "the call is coming from inside the house" bug.