Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution
by NeuraCryption on Thursday November 12, 2026 @03:28PM
(#50473721)
Is this exploitable? If it is, this is very serious and if this is an unpatched disclosure millions of Businesses around the world will be affected.
[ Parent
| on HN ]
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution
by mattashii on Thursday November 12, 2026 @03:39PM
(#50473918)
Yes, once you have logged in on a primary.
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution
by mdaniel on Thursday November 12, 2026 @03:46PM
(#50474019)
Isn't that only true if "millions of businesses" choose to hang their PG port out on the Internet with "allow 0/0"? In the spirit of being constructive, https://www.shodan.io/search?query=postgresql shows 516,000 which is definitely not none but pretty far from millions and based on skimming the results pretty far from the businesses part, too
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution
by mgiampapa on Thursday November 12, 2026 @04:02PM
(#50474237)
I would consider it a more useful lateral movement vector inside an existing org than anything else. Lots and lots of old postgress with weak acls inside networks.
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution
by insanitybit on Thursday November 12, 2026 @09:02PM
(#50477140)
I've had people tell me that they trust postres RLS as their security boundary and that it's fine to expose.
Re:22-Year-Old PostgreSQL Bug Turned into Remote Code Execution
by InsidiousWombat on Thursday November 12, 2026 @07:26PM
(#50476468)
Eh, any sensible one would have DB only accessible to app that uses it