CVE Intelligence
High

CVE-2026-111440 — JDBC LogFactory 任意类加载/构造导致潜在 RCE

在 openGauss-connector-jdbc 的 pgjdbc/src/main/java/org/postgresql/log/LogFactory.java 中，LogFactory 根据 JDBC 连接参数中的 logger 类名调用 Class.forName 加载类后，直接反射调用以 String 为参数的构造函数，再转换为 Log。缺少 asSubclass(Log.class) 校验，非 Log 实现类也会在类型检查前被实例化。因此，当攻击者可控制 JDBC URL 或连接属性中的 logger 类名，且客户端 classpath 中存在可被加载的类时，可能在客户端触发非预期的类加载与构造副作用。 此漏洞自 JDBC 1.1.0引入，影响 1.1.0 及之后的 2.x、3.x、5.x、6.x 各版本及补丁（含 6.0.0 分支最新 6.0.6），以及 7.0.0-RC1、7.0.0-RC2、7.0.0-RC3，并在 7.0.0-LTS 版本修复。修复在 Class.forName 之后先执行 asSubclass(Log.class)，仅允许 Log 子类进入构造。修复pr见https://gitcode.com/opengauss/openGauss-connector-jdbc/pull/423。

Published Oct 19, 2026 · Updated Oct 19, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: openGauss

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+2
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.22%
ahead of 12% of scored CVEs · Oct 19, 2026
Affects
openGauss-server
openGauss-connector-jdbc
CVSS base
7.0
High · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (openGauss-server openGauss-connector-jdbc).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
openGauss-server openGauss-connector-jdbc version 1.0.0, 1.0.1, 1.1.0version 2.0.0, 2.1.0version 3.0.0-3.0.5version 5.0.0-5.0.3version 5.1.0version 5.0.0-RC1version 6.0.0-RC1version 6.0.0-6.0.6
and 2 more version 7.0.0-RC1, 7.0.0-RC2, 7.0.0-RC3version 3.1.0-3.1.1
Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.0 CVSS 3.1 High 1.0 5.9 a1a479f7-907b-4ae8-a999-9148cadc9224 via NIST National Vulnerability Database
7.0 CVSS 3.1 High — — openGauss via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: a1a479f7-907b-4ae8-a999-9148cadc9224)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-470

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Received → Deferred
    Oct 19, 2026 · NIST National Vulnerability Database
  • SSVC assessment updated
    Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
  • Affected products removed · 1
    Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
  • Affected products added · opengauss-server/opengauss-connector-jdbc
    Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
  • Affected products added · opengauss-server/opengauss-connector-jdbc
    Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 19, 2026
  • CVSS changed · 7.0
    Oct 19, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 19, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 19, 2026 · Alertas do Telegram
  • CVE published
    Oct 19, 2026 · openGauss

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 19, 2026 – Oct 19, 2026
  • 1× Official description updated · Oct 19, 2026 – Oct 19, 2026

References

1 on the record

Elsewhere on this site

openGauss-server
every CVE for this vendor
CWE-470
other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-111440 is "JDBC LogFactory 任意类加载/构造导致潜在 RCE", rated High. It affects openGauss-connector-jdbc (openGauss-server); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.0 describes technical severity. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.