{"description":"Trending threats, MITRE ATT\u0026CK coverage, and detection metadata. Fed continuously.","favicon":"https://feed.craftedsignal.io/favicon-32x32.png","feed_url":"https://feed.craftedsignal.io/tags/psqlodbc/feed.json","home_page_url":"https://feed.craftedsignal.io/","icon":"https://feed.craftedsignal.io/apple-touch-icon.png","items":[{"_cs_actors":[],"_cs_cpes":[],"_cs_cves":[{"cvss":7.5,"id":"CVE-2026-120057"},{"cvss":7.1,"id":"CVE-2026-120065"}],"_cs_exploited":false,"_cs_has_poc":false,"_cs_poc_references":[],"_cs_products":["psqlODBC (versions before 18.00.0006)","psqlODBC (\u003c 18.00.0006)"],"_cs_severities":["high"],"_cs_tags":["vulnerability","memory-corruption","psqlodbc","postgresql"],"_cs_type":"advisory","_cs_vendors":[],"content_html":"\u003cp\u003eA memory corruption vulnerability exists in the psqlODBC driver. During large-object read (loread) operations, the driver copies data into the application's buffer using the length provided by the server without comparing it to the actual buffer size. An untrusted server or a man-in-the-middle can provide an excessive length, causing the driver to return more bytes than the buffer can hold, resulting in an overwrite of adjacent memory in the client process. Fetching any large-object column can trigger this condition.\u003c/p\u003e\n","date_modified":"2026-11-02T21:51:56Z","date_published":"2026-11-02T19:49:40Z","id":"https://feed.craftedsignal.io/briefs/2026-11-psqlodbc-memory-corruption/","summary":"The psqlODBC driver is vulnerable to memory corruption during loread operations because it fails to validate server-provided data lengths against buffer sizes.","title":"PostgreSQL: psqlODBC memory corruption via large-object read (CVE-2026-120057)","url":"https://feed.craftedsignal.io/briefs/2026-11-psqlodbc-memory-corruption/"}],"language":"en","title":"CraftedSignal Threat Feed - Psqlodbc","version":"https://jsonfeed.org/version/1.1"}