{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-105614 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-105614 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-105614 is a medium-severity vulnerability in DALIBO PostgreSQL Anonymizer, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-105614 and fix it if it is affected.\n\nWhat it is: CVE-2026-105614 is a medium-severity vulnerability in DALIBO PostgreSQL Anonymizer, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-105614 in the wild and no public exploit code.\n\nAffected product: DALIBO PostgreSQL Anonymizer. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-105614/ (Markdown: https://insights.sbomify.com/CVE-2026-105614/index.md)","id":"CVE-2026-105614","markdown":"https://insights.sbomify.com/CVE-2026-105614/index.md","name":"CVE-2026-105614","record":{"aliases":["GHSA-2wgx-cxvp-mvpw"],"analysis":null,"analysis_generated_by":null,"assigner":"PostgreSQL","cpe":[],"cvss":{"score":4.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-789","name":"Memory Allocation with Excessive Size Value"}],"description":"PostgreSQL Anonymizer's `anon.image_blur()` function doesn't check the declared dimension of the provided image, allowing an attacker to provide a small image with enormous declared dimensions. This vulnerability can be exploited to exhaust the memory of a backend and OOM-kill it (when ovecommit is on), which results in a cluster-wide crash recovery. The problem is resolved in PostgreSQL Anonymizer 3.3.0 and later versions.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"PostgreSQL Anonymizer: Unbounded image-decode memory allocation (DoS) in anon.image_blur()","id":"CVE-2026-105614","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"PostgreSQL Anonymizer: Masked roles can read the statistics of masked columns in pg_stats","id":"CVE-2026-105615"},"packages":[],"prev":{"headline":"PostgreSQL Anonymizer: Unbounded memory allocation (DoS) in range-based dummy functions","id":"CVE-2026-105613"},"products":["PostgreSQL Anonymizer"],"published":"2026-10-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-28","vendors":["DALIBO"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-105614/"}