# CVE-2026-111438: check_hba_replication 认证与访问控制绕过

> Attackers can bypass internal connection checks in openGauss replication to read backup and log data via the replication protocol.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-65mg-g3fh-wfvj

## What is CVE-2026-111438?

CVE-2026-111438 is a medium-severity authentication bypass vulnerability in openGauss-server, published on 19 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

在 openGauss-server 的 src/common/backend/libpq/hba.cpp 中，复制连接认证存在访问控制绕过。hba_getauthmethod() 在处理 HADR/SW 复制发送方时，不要求 is_node_internal_connection()，直接调用 check_hba_replication()。check_hba_replication() 仅按 replication 标记做弱匹配，缺少普通 check_hba() 中的远程 trust 禁止等完整校验。因此，非内部网络的 HADR/SW 复制连接可绕过内部连接限制和完整 pg_hba 策略完成认证，进而通过复制协议读取备份与日志数据。

此问题随 HADR 复制发送方绕过内部连接校验进入代码，自 3.0.0 起即存在。受影响版本包括 3.0.x、3.1.x、5.0.x、5.1.0、6.0.x，以及 7.0.0-RC1、7.0.0-RC2、7.0.0-RC3。该问题已在 7.0.0-LTS版本修复，通过要求 HADR/SW 复制发送方必须经过 is_node_internal_connection 校验，使外部复制连接改走普通 check_hba() 并触发禁止远程 trust 策略。修复pr见https://gitcode.com/opengauss/openGauss-server/pull/9757。

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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


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

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

## Is CVE-2026-111438 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111438 is a medium-severity authentication bypass vulnerability in openGauss-server, published on 19 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-111438 in the wild and no public exploit code.

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

## Sources

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

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