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.newCreate a CVE report
Check your stack
CVE-2026-120066

psqlODBC log files are created with default permissions at a predictable path and follow symbolic links

Products / packages PostgreSQL psqlODBC

Published

Share

Severity and exploitation

Not in CISA KEV

KEV coverage does not rule out exploitation.

KEV checked 14/11/2026, 22:00:33 UTC
PostgreSQL · CVSS:3.1 · 5.3
Assessment vectorCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N

Severity

medium5.3

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Not established by this record

Missing evidence does not mean no public exploit exists.

Remediation

Source guidance available

Review the recorded instructions. Guidance may be a workaround rather than a fixed version.

What this means

psqlODBC versions before 18.00.0006 create log files with default permissions at a predictable path and follow symbolic links, allowing a local user to read or append log data. A local attacker can access query text and data from another user's logs. The weakness is due to incorrect permission assignment and improper link resolution.

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

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

PostgreSQL · PostgreSQL

psqlODBC

1 range
PostgreSQL version evidence

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

affected

0 → before 18.00.0006

custom versions

unaffected

unknown

Other versions: unaffected

Automatic dependency matching is unavailable for this record. Use the product evidence and publisher’s instructions to check your installation.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

Upgrade to psqlODBC 18.00.0006 or later. On Unix-like systems, log files are opened with mode 0600 and O_NOFOLLOW, and an existing log file is used only if it is a regular file owned by the user running the application.

PostgreSQL guidance ↗

Leave Debug and CommLog disabled in production. If logging is needed, set Logdir in the driver's section of odbcinst.ini (PostgreSQL Unicode or PostgreSQL ANSI) to a directory writable only by the user running the application.

PostgreSQL guidance ↗

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.

Original source description

Read the full publisher description

On Unix-like systems, when logging is enabled, psqlODBC creates its log files in /tmp by default, named from the program name, user name, and process ID, with the default permissions, typically world-readable, and follows symbolic links when opening them. A local user can read query text and data from another user's logs, and can place a symbolic link at the predictable path so that the driver appends log data to a file of the attacker's choosing with the victim's privileges. Versions before psqlODBC 18.00.0006 are affected.

References

1 sources
postgresql-interfaces/psqlodbc · security/advisories/GHSA-wj7r-6pj3-62g8
Vendor advisoryPostgreSQL

Inside the record

Evidence available

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

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

Original records

CVE-2026-120066

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

CWE-732 Incorrect Permission Assignment for Critical Resource

PostgreSQL

Related →
CWE-59 ↗

CWE-59 Improper Link Resolution Before File Access ('Link Following')

PostgreSQL

Related →
Contributing organizations · 2
PostgreSQL

Assigning organization

2026-11-02
CISA-ADP

Additional data publisher

2026-11-02

Timeline

All times UTC

  1. Advisory published

    Publication date supplied by the source.

  2. Source updated

    Latest modification date supplied by the source.

  3. Last imported by cve.new

    Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes
  1. CVE · CVE-2026-120066

    Observed 2026-11-02T19:46:08.301Z · upstream updated 2026-11-02T19:37:32.927Z

    Prioritization updated

    before

    []

    after

    [
  {
    "source": "CISA-ADP",
    "type": "SSVC",
    "role": "CISA Coordinator",
    "timestamp": "2026-11-02T19:37:21.337272Z",
    "decisions": [
      {
        "name": "Exploitation",
        "value": "none"
      },
      {
        "name": "Automatable",
        "value": "no"
      },
      {
        "name": "Technical Impact",
        "value": "partial"
      }
    ]
  }
]

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

Showing up to 50 most recent observed changes.