PostgreSQL Anonymizer: Unbounded image-decode memory allocation (DoS) in anon.image_blur()
Impact
PostgreSQL Anonymizer's `anon.image_blur()` function has an unbounded memory allocation weakness, allowing an attacker to exhaust backend memory. Affected versions are less than 3.3.0. This can cause a cluster-wide crash recovery.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.What to do
Revoke execution rights on the range-based dummy functions or drop them.
Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
DALIBO · PostgreSQL
PostgreSQL Anonymizer
1 range
DALIBO · PostgreSQL
PostgreSQL Anonymizer
Compare with this publisher’s ranges. This does not inspect your installation.
affected
1 → before 3.3.0
semver versions
Other versions: unaffected
Original source 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.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-105614View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 1
Assigning organization
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.