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
cve.new Create a CVE report
Check your stack
CVE-2026-105616medium5.7

PostgreSQL Anonymizer: The secret salt and shift of anon are readable by any role in pg_roles or pg_db_role_setting

Impact

PostgreSQL Anonymizer versions before 3.3.0 have a weakness where the secret salt and shift are readable by any role in pg_roles or pg_db_role_setting. This is an exposure of sensitive information. The issue is resolved in version 3.3.0 and later.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

What to do

Configure the salt in the postgresql.conf file (or one of it's includes).

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
PostgreSQL version evidence

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 restricts acces to the salt and shift via the SHOW command for users not member of pg_read_all_settings. But they are visible in pg_db_role_setting or pg_roles if they were set on the database, user or both. PostgreSQL Anonymizer's documentation recommends to use ALTER DATABASE / ALTER ROLE for the salt. 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-105616

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-200 ↗

Exposure of Sensitive Information to an Unauthorized Actor

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
gitlab.com/dalibo/postgresql_anonymizer/-/issues/694
Source referencePostgreSQL