dbcve.org
Use After FreeWeakness · CWE-416

CVE-2026-14178

MEDIUM · 5.9 CVSS v3.1 Published 2026-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
openGauss 在处理带 NLS 参数的 to_timestamp 调用时，to_timestamp_with_fmt_nls() 会将 nls_fmt_str 保存到 u_sess->parser_cxt.nls_fmt_str。在 seqscan + sort 执行路径下，该字符串原本被分配在 SeqScan 的表达式上下文中；当 SeqScan 完成后，该内存上下文会被 reset，但后续结果输出阶段 timestamp_out() 仍会通过 CheckNlsFormat() 访问 u_sess->parser_cxt.nls_fmt_str，导致访问已释放内存。攻击者在具备数据库 SQL 执行权限的情况下，可构造特定 to_timestamp(..., ..., nlsparam) 查询触发 heap-use-after-free。在 ASan/Memcheck 环境下表现为数据库服务退出；在实际运行环境中可能造成后端进程异常退出，影响数据库服务可用性，形成拒绝服务风险。该问题在openGauss-server-7.0.0-RC1版本和openGauss-server-7.0.0-RC2版本存在，目前已在openGauss-server-7.0.0-RC3版本修复。由于 openGauss-server-7.0.0-RC1版本和openGauss-server-7.0.0-RC2均为创新版本，不会发布针对性补丁包，涉及版本升级至 openGauss-server-7.0.0-RC3或更新版本即可。

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

openGauss has a heap-use-after-free vulnerability in to_timestamp() with NLS parameters. The nls_fmt_str is stored in u_sess->parser_cxt.nls_fmt_str but allocated in the SeqScan expression context, which gets reset after SeqScan completes. Later, timestamp_out() accesses this freed memory through CheckNlsFormat() during result output, causing a use-after-free.

MitigationUpgrade openGauss-server to version 7.0.0-RC3 or newer to resolve this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check openGauss server version
    Run 'SELECT version();' or 'gaussdb --version' to determine the installed version
    Affected if Version is earlier than 7.0.0-RC3 (the fixed release)
  2. Verify to_timestamp function usage with NLS parameters
    Review application SQL queries and database logs for use of to_timestamp() with explicit NLS format strings (such as 'NLS_DATE_FORMAT' or similar)
    Affected if The to_timestamp() function is called with NLS format parameters in any query
  3. Confirm NLS parameter configuration is active
    Check session or database parameters for NLS-related settings: query 'SHOW all;' or check 'pg_settings' for NLS_DATE_FORMAT, NLS_TIMESTAMP_FORMAT, or similar NLS environment variables
    Affected if NLS date/timestamp format parameters are configured or set in the session context
  4. Identify query execution path through SeqScan
    Analyze query execution plans (EXPLAIN/EXPLAIN ANALYZE) for queries using to_timestamp() with NLS to confirm they pass through SeqScan node execution
    Affected if Queries using to_timestamp with NLS parameters are executed via SeqScan plan nodes (the vulnerable execution path)

A user is affected if they run openGauss version earlier than 7.0.0-RC3 AND execute to_timestamp() with NLS format parameters, where the query plan involves SeqScan execution that triggers the vulnerable code path in timestamp_out().

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade openGauss-server to version 7.0.0-RC3 or newer to resolve this vulnerability.

Recommended fix High confidence

openGauss-server-7.0.0-RC3 or later

  1. 1. Identify all openGauss-server installations running version 7.0.0-RC1 or 7.0.0-RC2
  2. 2. Schedule a maintenance window for the upgrade
  3. 3. Backup the existing database data and configuration files
  4. 4. Download openGauss-server-7.0.0-RC3 or a newer stable release from the official openGauss repository
  5. 5. Stop the openGauss database service
  6. 6. Install the new openGauss-server-7.0.0-RC3 (or newer) version
  7. 7. Start the openGauss database service
  8. 8. Verify the database is operational and test the to_timestamp function with NLS parameters to confirm the vulnerability is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14178 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-14178 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data