Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
Check your stack
CVE-2026-105614medium4.7

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.

PostgreSQL guidance

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

DALIBO · PostgreSQL

PostgreSQL Anonymizer

1 range

Compare with this publisher’s ranges. This does not inspect your installation.

affected

1 → before 3.3.0

semver versions

unaffected

unknown

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

Package identity · not supplied
Version evidence
Remediation guidance
Weakness classification
Additional publishers · not supplied

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-105614

View 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.

CWE-789 ↗

Memory Allocation with Excessive Size Value

PostgreSQL

Related →
Contributing organizations · 1
PostgreSQL

Assigning organization

2026-10-28

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

1 sources