CGA-PXQ6-3GJC-M265: confluent-common-docker
CVSS: UnknownUnknown
Published Date unknownLast modified Date unknown
Status not reported
The data service did not report a status for this record. Only the available sections are shown.Vulnerability summary
CGA-PXQ6-3GJC-M265 is a vulnerability in confluent-common-docker with no CVSS score yet.
CVSS score
Not scored
010
No CVSS score recordedEPSS score
Not scored
0%100%
No EPSS score yetKEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded
Advisory lineage
Upstream 0 · Downstream 0 · Related 1Timeline
No timeline events recorded.
Description
No description has been published for this record.
CVSS metrics
Risk metrics not yet published.
EPSS trend
No EPSS score has been published for this record yet.
Known exploited
Compare KEV catalogsNot in any of the 3 tracked catalogs.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root causeNo weakness data has been published for this record.
Affected systems
Chainguard77 products
- confluent-common-docker< 7.6.9-r0
- confluent-kafka< 8.2.0.367-r0
- hive< 4.0.1-r1
- hive-compat< 4.0.1-r1
- kafka< 3.7.0-r2
- kafka-bitnami-compat< 3.7.0-r2
- kafka-jre-bcfips< 3.7.1-r0
- solr< 9.5.0-r2
- spark-3.5-scala-2.13< 3.5.7-r2
- tez< 0.10.4-r6
- trino< 443-r0
- trino-config< 443-r0
- trino-oci-entrypoint< 443-r0
- trino-plugin-accumulo< 443-r0
- trino-plugin-ai-functions< 443-r0
- trino-plugin-atop< 443-r0
- trino-plugin-bigquery< 443-r0
- trino-plugin-blackhole< 443-r0
- trino-plugin-cassandra< 443-r0
- trino-plugin-clickhouse< 443-r0
- trino-plugin-delta-lake< 443-r0
- trino-plugin-druid< 443-r0
- trino-plugin-duckdb< 443-r0
- trino-plugin-elasticsearch< 443-r0
- trino-plugin-example-http< 443-r0
- trino-plugin-exasol< 443-r0
- trino-plugin-exchange-filesystem< 443-r0
- trino-plugin-exchange-hdfs< 443-r0
- trino-plugin-faker< 443-r0
- trino-plugin-functions-python< 443-r0
- trino-plugin-geospatial< 443-r0
- trino-plugin-google-sheets< 443-r0
- trino-plugin-hive< 443-r0
- trino-plugin-http-event-listener< 443-r0
- trino-plugin-http-server-event-listener< 443-r0
- trino-plugin-hudi< 443-r0
- trino-plugin-iceberg< 443-r0
- trino-plugin-ignite< 443-r0
- trino-plugin-jmx< 443-r0
- trino-plugin-kafka< 443-r0
- trino-plugin-kafka-event-listener< 443-r0
- trino-plugin-kinesis< 443-r0
- trino-plugin-kudu< 443-r0
- trino-plugin-lakehouse< 443-r0
- trino-plugin-ldap-group-provider< 443-r0
- trino-plugin-local-file< 443-r0
- trino-plugin-loki< 443-r0
- trino-plugin-mariadb< 443-r0
- trino-plugin-memory< 443-r0
- trino-plugin-ml< 443-r0
- trino-plugin-mongodb< 443-r0
- trino-plugin-mysql< 443-r0
- trino-plugin-mysql-event-listener< 443-r0
- trino-plugin-opa< 443-r0
- trino-plugin-openlineage< 443-r0
- trino-plugin-opensearch< 443-r0
- trino-plugin-oracle< 443-r0
- trino-plugin-password-authenticators< 443-r0
- trino-plugin-phoenix5< 443-r0
- trino-plugin-pinot< 443-r0
- trino-plugin-postgresql< 443-r0
- trino-plugin-prometheus< 443-r0
- trino-plugin-ranger< 443-r0
- trino-plugin-raptor-legacy< 443-r0
- trino-plugin-redis< 443-r0
- trino-plugin-redshift< 443-r0
- trino-plugin-resource-group-managers< 443-r0
- trino-plugin-session-property-managers< 443-r0
- trino-plugin-singlestore< 443-r0
- trino-plugin-snowflake< 443-r0
- trino-plugin-spooling-filesystem< 443-r0
- trino-plugin-sqlserver< 443-r0
- trino-plugin-teradata-functions< 443-r0
- trino-plugin-thrift< 443-r0
- trino-plugin-tpcds< 443-r0
- trino-plugin-tpch< 443-r0
- trino-plugin-vertica< 443-r0
Wolfi74 products
- confluent-common-docker< 7.6.9-r0
- confluent-kafka< 8.2.0.367-r0
- kafka< 3.7.0-r2
- kafka-bitnami-compat< 3.7.0-r2
- solr< 9.5.0-r2
- spark-3.5-scala-2.13< 3.5.7-r2
- tez< 0.10.4-r6
- trino< 443-r0
- trino-config< 443-r0
- trino-oci-entrypoint< 443-r0
- trino-plugin-accumulo< 443-r0
- trino-plugin-ai-functions< 443-r0
- trino-plugin-atop< 443-r0
- trino-plugin-bigquery< 443-r0
- trino-plugin-blackhole< 443-r0
- trino-plugin-cassandra< 443-r0
- trino-plugin-clickhouse< 443-r0
- trino-plugin-delta-lake< 443-r0
- trino-plugin-druid< 443-r0
- trino-plugin-duckdb< 443-r0
- trino-plugin-elasticsearch< 443-r0
- trino-plugin-example-http< 443-r0
- trino-plugin-exasol< 443-r0
- trino-plugin-exchange-filesystem< 443-r0
- trino-plugin-exchange-hdfs< 443-r0
- trino-plugin-faker< 443-r0
- trino-plugin-functions-python< 443-r0
- trino-plugin-geospatial< 443-r0
- trino-plugin-google-sheets< 443-r0
- trino-plugin-hive< 443-r0
- trino-plugin-http-event-listener< 443-r0
- trino-plugin-http-server-event-listener< 443-r0
- trino-plugin-hudi< 443-r0
- trino-plugin-iceberg< 443-r0
- trino-plugin-ignite< 443-r0
- trino-plugin-jmx< 443-r0
- trino-plugin-kafka< 443-r0
- trino-plugin-kafka-event-listener< 443-r0
- trino-plugin-kinesis< 443-r0
- trino-plugin-kudu< 443-r0
- trino-plugin-lakehouse< 443-r0
- trino-plugin-ldap-group-provider< 443-r0
- trino-plugin-local-file< 443-r0
- trino-plugin-loki< 443-r0
- trino-plugin-mariadb< 443-r0
- trino-plugin-memory< 443-r0
- trino-plugin-ml< 443-r0
- trino-plugin-mongodb< 443-r0
- trino-plugin-mysql< 443-r0
- trino-plugin-mysql-event-listener< 443-r0
- trino-plugin-opa< 443-r0
- trino-plugin-openlineage< 443-r0
- trino-plugin-opensearch< 443-r0
- trino-plugin-oracle< 443-r0
- trino-plugin-password-authenticators< 443-r0
- trino-plugin-phoenix5< 443-r0
- trino-plugin-pinot< 443-r0
- trino-plugin-postgresql< 443-r0
- trino-plugin-prometheus< 443-r0
- trino-plugin-ranger< 443-r0
- trino-plugin-raptor-legacy< 443-r0
- trino-plugin-redis< 443-r0
- trino-plugin-redshift< 443-r0
- trino-plugin-resource-group-managers< 443-r0
- trino-plugin-session-property-managers< 443-r0
- trino-plugin-singlestore< 443-r0
- trino-plugin-snowflake< 443-r0
- trino-plugin-spooling-filesystem< 443-r0
- trino-plugin-sqlserver< 443-r0
- trino-plugin-teradata-functions< 443-r0
- trino-plugin-thrift< 443-r0
- trino-plugin-tpcds< 443-r0
- trino-plugin-tpch< 443-r0
- trino-plugin-vertica< 443-r0
2 vendors · 151 products
References
0 linksNo references have been published for this record.
Related vulnerabilities
CVE-2025-52999chainguardcassandra-4.0+2360.77%jackson-core contains core low-level incremental ("streaming") parser and generator abstractions used by Jackson Data Processor. In versions prior to 2.15.0, if a user parses an input file and it has deeply nested data, Jackson could end up throwing a StackoverflowError if the depth is particularly large. jackson-core 2.15.0 contains a configurable limit for how deep Jackson will traverse in an input document, defaulting to an allowable depth of 1000. jackson-core will throw a StreamConstraintsException if the limit is reached. jackson-databind also benefits from this change because it uses jackson-core to parse JSON inputs. As a workaround, users should avoid parsing input files from untrusted sources.CVE-2025-11143chainguardakhq+1860.16%The Jetty URI parser has some key differences to other common parsers when evaluating invalid or unusual URIs. Differential parsing of URIs in systems using multiple components may result in security by-pass. For example a component that enforces a black list may interpret the URIs differently from one that generates a response. At the very least, differential parsing may divulge implementation details.CVE-2025-68161apache software foundationapache log4j core+2410.77%The Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName configuration attribute or the log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName system property is set to true.
This issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions:
* The attacker is able to intercept or redirect network traffic between the client and the log receiver.
* The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured).
Users are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue.
As an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.CVE-2025-47907chainguardaactl+45350.38%Cancelling a query (e.g. by cancelling the context passed to one of the query methods) during a call to the Scan method of the returned Rows can result in unexpected results if other queries are being made in parallel. This can result in a race condition that may overwrite the expected results with those of another query, causing the call to Scan to return either unexpected results from the other query or an error.CVE-2025-47906chainguardaddon-resizer+3100.55%If the PATH environment variable contains paths which are executables (rather than just directories), passing certain strings to LookPath ("", ".", and ".."), can result in the binaries listed in the PATH being unexpectedly returned.CVE-2025-48734apache software foundationapache commons beanutils 1.x+2621.82%Improper Access Control vulnerability in Apache Commons.
A special BeanIntrospector class was added in version 1.9.2. This can be used to stop attackers from using the declared class property of Java enum objects to get access to the classloader. However this protection was not enabled by default. PropertyUtilsBean (and consequently BeanUtilsBean) now disallows declared class level property access by default.
Releases 1.11.0 and 2.0.0-M2 address a potential security issue when accessing enum properties in an uncontrolled way. If an application using Commons BeanUtils passes property paths from an external source directly to the getProperty() method of PropertyUtilsBean, an attacker can access the enum’s class loader via the “declaredClass” property available on all Java “enum” objects. Accessing the enum’s “declaredClass” allows remote attackers to access the ClassLoader and execute arbitrary code. The same issue exists with PropertyUtilsBean.getNestedProperty().
Starting in versions 1.11.0 and 2.0.0-M2 a special BeanIntrospector suppresses the “declaredClass” property. Note that this new BeanIntrospector is enabled by default, but you can disable it to regain the old behavior; see section 2.5 of the user's guide and the unit tests.
This issue affects Apache Commons BeanUtils 1.x before 1.11.0, and 2.x before 2.0.0-M2.Users of the artifact commons-beanutils:commons-beanutils
1.x are recommended to upgrade to version 1.11.0, which fixes the issue.
Users of the artifact org.apache.commons:commons-beanutils2
2.x are recommended to upgrade to version 2.0.0-M2, which fixes the issue.