# CVE-2026-14178: openGauss存在非法内存访问导致DoS漏洞

> An attacker with SQL execution privileges can trigger a use-after-free in openGauss via crafted to_timestamp queries, causing denial of service.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jun 2026
- **Updated:** 30 Jun 2026
- **Also known as:** GHSA-v555-5g3c-vq2x

## What is CVE-2026-14178?

CVE-2026-14178 is a medium-severity use after free vulnerability in openGauss-server-7.0.0-RC1, published on 30 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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或更新版本即可。

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2026-14178?


## How do I fix CVE-2026-14178?

No fix has been published for CVE-2026-14178 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-14178 being exploited?

There is no known exploitation of CVE-2026-14178 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14178 and fix it if it is affected.

What it is: CVE-2026-14178 is a medium-severity use after free vulnerability in openGauss-server-7.0.0-RC1, published on 30 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14178 in the wild and no public exploit code.

Affected product: openGauss-server-7.0.0-RC1. 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-14178/ (Markdown: https://insights.sbomify.com/CVE-2026-14178/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-14178
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-14178
- OSV: https://osv.dev/vulnerability/CVE-2026-14178

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-14178/
Summaries are generated and may contain mistakes; the official description above is the record.