CVE-2026-14178

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-40326 (ENISA EUVD) · GHSA-v555-5g3c-vq2x (GitHub Security Advisories)Source: ENISA EUVD

5.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.9Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (openGauss Community) lists openGauss-server-7.0.0-RC3 versions openGauss-server-7.0.0-RC3 as unaffected. No release containing a fix is confirmed on record.

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.9MEDIUMmedium confidence
EG Risk
27
EG Risk 27/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity59% × 45%
Impact severity (EG Severity): CVSS 5.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
30th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.9): severity, escalated by confirmed exploitation. This CVE's 5.9 is its impact severity (EG Severity), not escalated.

EG Severity
5.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 30, 2026

Last Modified

June 30, 2026

Advisory Details (1)

Auto-updated Jun 30, 2026
No fix on record yet.
Web page

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 8× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 203 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 103 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  2. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  3. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  4. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  5. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  6. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  7. 2026-10-25 14:48 UTCEG score recompute
  8. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  9. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  10. 2026-10-23 06:40 UTCEG score recompute
  11. 2026-10-23 06:40 UTCGHSA enrichmentGHSA-v555-5g3c-vq2x · GitHub CVSS 5.9
  12. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  13. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  14. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  15. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  16. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  17. 2026-10-18 05:02 UTCEG score recompute
  18. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  19. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  20. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  21. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  22. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  23. 2026-10-12 16:34 UTCEG score recompute
  24. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  25. 2026-10-11 20:11 UTCEG score recompute
Show 75 more
  1. 2026-10-11 18:23 UTCEG score recompute
  2. 2026-10-11 14:56 UTCEG score recompute
  3. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  4. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  5. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  6. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  7. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  8. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  9. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  10. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  11. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  12. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  13. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  14. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  15. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  16. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  17. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  18. 2026-09-23 07:21 UTCEG score recompute
  19. 2026-09-23 07:21 UTCGHSA enrichmentGHSA-v555-5g3c-vq2x · GitHub CVSS 5.9
  20. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-09-18 06:50 UTCEG score recompute
  22. 2026-09-18 06:50 UTCGHSA enrichmentGHSA-v555-5g3c-vq2x · GitHub CVSS 5.9
  23. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  24. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  25. 2026-09-14 00:48 UTCEG score recompute
  26. 2026-09-14 00:48 UTCGHSA enrichmentGHSA-v555-5g3c-vq2x · GitHub CVSS 5.9
  27. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  28. 2026-09-12 15:10 UTCEG score recompute
  29. 2026-09-12 15:10 UTCGHSA enrichmentGHSA-v555-5g3c-vq2x · GitHub CVSS 5.9
  30. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  31. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  32. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  33. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  34. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  35. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  36. 2026-09-06 14:36 UTCEG score recompute
  37. 2026-09-06 14:36 UTCGHSA enrichmentGHSA-v555-5g3c-vq2x · GitHub CVSS 5.9
  38. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  39. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  40. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  41. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  42. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  43. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  44. 2026-08-30 18:09 UTCEG score recompute
  45. 2026-08-30 18:09 UTCGHSA enrichmentGHSA-v555-5g3c-vq2x · GitHub CVSS 5.9
  46. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  47. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  48. 2026-08-27 22:42 UTCEG score recompute
  49. 2026-08-27 22:42 UTCGHSA enrichmentGHSA-v555-5g3c-vq2x · GitHub CVSS 5.9
  50. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  51. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  52. 2026-08-24 11:44 UTCEG score recompute
  53. 2026-08-24 11:44 UTCGHSA enrichmentGHSA-v555-5g3c-vq2x · GitHub CVSS 5.9
  54. 2026-08-23 08:27 UTCEG score recompute
  55. 2026-08-23 08:27 UTCGHSA enrichmentGHSA-v555-5g3c-vq2x · GitHub CVSS 5.9
  56. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  57. 2026-08-22 08:27 UTCEG score recompute
  58. 2026-08-22 08:27 UTCGHSA enrichmentGHSA-v555-5g3c-vq2x · GitHub CVSS 5.9
  59. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  60. 2026-08-21 06:37 UTCEG score recompute
  61. 2026-08-21 06:37 UTCGHSA enrichmentGHSA-v555-5g3c-vq2x · GitHub CVSS 5.9
  62. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  63. 2026-08-20 06:47 UTCEG score recompute
  64. 2026-08-20 06:47 UTCGHSA enrichmentGHSA-v555-5g3c-vq2x · GitHub CVSS 5.9
  65. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  66. 2026-08-19 06:57 UTCEG score recompute
  67. 2026-08-19 06:56 UTCGHSA enrichmentGHSA-v555-5g3c-vq2x · GitHub CVSS 5.9
  68. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  69. 2026-08-18 06:22 UTCEG score recompute
  70. 2026-08-18 06:22 UTCGHSA enrichmentGHSA-v555-5g3c-vq2x · GitHub CVSS 5.9
  71. 2026-08-16 20:04 UTCEG score recompute
  72. 2026-08-16 20:04 UTCGHSA enrichmentGHSA-v555-5g3c-vq2x · GitHub CVSS 5.9
  73. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  74. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  75. 2026-08-15 20:14 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-14178?
CVE-2026-14178 is a medium-severity vulnerability; its CVE record was 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 made public?
CVE-2026-14178 was made public on June 30, 2026: that is the date its CVE record's CNA, openGauss Community, gives for when the vulnerability was made public. The CVE record itself was published on June 30, 2026. EchelonGraph's copy of the record carries a last-modified date of June 30, 2026; the record at its source may have been updated since.
Is CVE-2026-14178 actively exploited?
CVE-2026-14178 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-14178?
CVE-2026-14178 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-14178?
No fix for CVE-2026-14178 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (openGauss Community) lists openGauss-server-7.0.0-RC3 versions openGauss-server-7.0.0-RC3 as unaffected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-14178 are linked in the Vendor Advisories panel on this page.

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.