CVE-2026-105613 PostgreSQL Anonymizer: Unbounded memory allocation (DoS) in range-based dummy functions
Medium 4.7
Published
Updated
Check this codebase for CVE-2026-105613 and fix it if it is affected.
What it is: CVE-2026-105613 is a medium-severity vulnerability in DALIBO PostgreSQL Anonymizer, published on 28 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-105613 in the wild and no public exploit code.
Affected product: DALIBO PostgreSQL Anonymizer. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-105613/ (Markdown: https://insights.sbomify.com/CVE-2026-105613/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-105613?
CVE-2026-105613 is a medium-severity vulnerability in DALIBO PostgreSQL Anonymizer, published on 28 Oct 2026.
Official description
PostgreSQL Anonymizer's range-based dummy functions dont constraint the range size. 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.
Weakness: CWE-789
Which versions are affected by CVE-2026-105613?
How do I fix CVE-2026-105613?
No fix has been published for CVE-2026-105613 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-105613 being exploited?
There is no known exploitation of CVE-2026-105613 in the wild and no public exploit code.
Sources
Also known as GHSA-4mxh-vp96-jp43.