CVE-2026-14178

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreHIGH confidence

Score 5.9 from GitHub Security Advisory published 2026-06-30. a secondary CVSS source baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
5.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
5.9
EG Score
5.9(high)
EPSS
27.1%
KEV
Not listed

Published

June 30, 2026

Last Modified

June 30, 2026

Advisory Details (1)

Auto-updated Jun 30, 2026
No patch confirmed yet.
generic

AtomGit - 全球开发者的开源社区,开源代码托管平台

https://gitcode.com/opengauss/openGauss-server/pull/8877

Vendor Advisories for CVE-2026-14178(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 13:31 UTCEG score recompute
  3. 2026-07-06 13:31 UTCGHSA enrichment
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 13:41 UTCEG score recompute
  6. 2026-07-05 13:41 UTCGHSA enrichment
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 13:52 UTCEG score recompute
  10. 2026-07-04 13:51 UTCGHSA enrichment
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-03 14:01 UTCEG score recompute
  13. 2026-07-03 14:01 UTCGHSA enrichment
  14. 2026-07-02 14:11 UTCEG score recompute
  15. 2026-07-02 14:11 UTCGHSA enrichment
  16. 2026-07-01 15:06 UTCEPSS rescore
  17. 2026-07-01 15:06 UTCEPSS rescore
  18. 2026-07-01 14:22 UTCEG score recompute
  19. 2026-07-01 14:22 UTCGHSA enrichment
  20. 2026-06-30 14:33 UTCEG score recompute
  21. 2026-06-30 14:32 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-14178?
CVE-2026-14178 is a medium vulnerability published on June 30, 2026. openGauss 在处理带 NLS 参数的 totimestamp 调用时，totimestampwithfmtnls() 会将 nlsfmtstr 保存到 usess->parsercxt.nlsfmtstr。在 seqscan + sort 执行路径下，该字符串原本被分配在 SeqScan 的表达式上下文中；当 SeqScan 完成后，该内存上下文会被 reset，但后续结果输出阶段 timestampout() 仍会通过 CheckNlsFormat() 访问 usess->parsercxt.nlsfmtstr，导致访问已释放内存。攻击者在具备数据库 SQL…
When was CVE-2026-14178 disclosed?
CVE-2026-14178 was first published in the National Vulnerability Database on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14178 actively exploited?
CVE-2026-14178 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-14178?
CVE-2026-14178 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-14178?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14178, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-14178

Explore →

Is Your Infrastructure Affected by CVE-2026-14178?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs