# CVE-2026-111440: openGauss JDBC Connector arbitrary class instantiation via logger parameter

Source: https://junglewise.ai/threats/cve-2026-111440-opengauss-connector-jdbc-pgjdbc-src-main-java-org-postgresql-log  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-19. Updated: 2026-10-19  
License: CC BY 4.0 with a link back

CVE-2026-111440 · Severity: high · CVSS 7 · Published 2026-10-19

openGauss JDBC Connector is a database client library for Java applications. An attacker who can control the JDBC connection URL or properties can specify an arbitrary logger class name that gets loaded and instantiated on the client, potentially triggering unintended code execution or application behavior if a gadget class exists in the classpath. This allows remote code execution or denial of service depending on what classes are available to the application.

Vendors: [openGauss](https://junglewise.ai/threats/vendors/opengauss).

## Quick answers

**Is CVE-2026-111440 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-111440 being exploited in the wild.

**How severe is CVE-2026-111440?** High severity, with a CVSS score of 7, published 19 October 2026.

**Which products and versions are affected?** openGauss JDBC Connector 1.1.0 through 6.0.6, 7.0.0-RC1, 7.0.0-RC2, 7.0.0-RC3.

**Is there a fix for CVE-2026-111440?** Yes: fixed in 7.0.0-LTS. Until then: Restrict access to JDBC connection strings and connection property configuration to trusted sources only, or upgrade to version 7.0.0-LTS or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-111440 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-111440?** Check whether you run openGauss JDBC Connector at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 7.0.0-LTS

Restrict access to JDBC connection strings and connection property configuration to trusted sources only, or upgrade to version 7.0.0-LTS or later.

## Technical details

The LogFactory class in openGauss-connector-jdbc uses Class.forName() to load a logger class specified via JDBC connection parameters, then directly instantiates it via reflection with a String argument constructor without validating that the loaded class implements the Log interface. An attacker controlling the JDBC URL or connection properties can supply a malicious class name (if a gadget class exists in the classpath) to trigger arbitrary instantiation side effects. The fix validates the loaded class with asSubclass(Log.class) before instantiation.

## Affected products

- openGauss JDBC Connector 1.1.0 through 6.0.6, 7.0.0-RC1, 7.0.0-RC2, 7.0.0-RC3

## Timeline

- 2026-10-19: disclosed

## References

- [https://opengauss.org/zh/download/archive/?version=7.0.0-RC3](https://opengauss.org/zh/download/archive/?version=7.0.0-RC3)
- [https://gitcode.com/opengauss/openGauss-connector-jdbc/pull/423](https://gitcode.com/opengauss/openGauss-connector-jdbc/pull/423)