CVE-2026-14178
Last modified
CVE-2026-14178 is a medium-severity vulnerability rated 5.9/10 on the CVSS scale. 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或更新版本即可。.
Description
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或更新版本即可。
Metrics
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| openGauss-server | openGauss-server-7.0.0-RC2 | openGauss-server-7.0.0-RC2 |
| openGauss-server | openGauss-server-7.0.0-RC1 | openGauss-server-7.0.0-RC1 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-14178?
How severe is CVE-2026-14178?
How do I fix CVE-2026-14178?
Related CVEs from 2026
- CVE-2026-1416A security flaw has been discovered in GPAC up to 2.4.0. Aff…3.3
- CVE-2026-14160Time-of-check time-of-use (TOCTOU) race condition vulnerabil…5.9
- CVE-2026-14161Hospital Quening Management developed by Advantech has a Sen…8.7
- CVE-2026-14162Hospital Queuing Management developed by Advantech has a Sen…9.8
- CVE-2026-14164A double free issue has been identified in libarchive's RAR5…7.5
- CVE-2026-1417A weakness has been identified in GPAC up to 2.4.0. Affected…3.3
- CVE-2026-1418A security vulnerability has been detected in GPAC up to 2.4…7.8
- CVE-2026-14181@fastify/middie versions 9.1.0 through 9.3.2 fail to guard t…7.5
- CVE-2026-1419A weakness has been identified in D-Link DCS700l 1.03.09. Af…7.2
- CVE-2026-14191An out-of-bounds heap write exists in the RAR5 recovery-volu…7.8
- CVE-2026-14193DVP80ES300T with Improper Validation of Array Index Vulnerab…7.5
- CVE-2026-14198@fastify/middie versions 9.1.0 through 9.3.2 decode the enco…9.1
Are you affected by CVE-2026-14178?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
