CGA-73J6-9258-JQFX: opensearch-2
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-73J6-9258-JQFX is a vulnerability in opensearch-2 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
Chainguard83 products
- opensearch-2< 2.19.1-r0
- opensearch-2-alerting< 2.19.1-r0
- opensearch-2-analysis-icu< 2.19.1-r0
- opensearch-2-analysis-kuromoji< 2.19.1-r0
- opensearch-2-analysis-nori< 2.19.1-r0
- opensearch-2-analysis-phonetic< 2.19.1-r0
- opensearch-2-analysis-smartcn< 2.19.1-r0
- opensearch-2-analysis-stempel< 2.19.1-r0
- opensearch-2-analysis-ukrainian< 2.19.1-r0
- opensearch-2-anomaly-detection< 2.19.1-r0
- opensearch-2-asynchronous-search< 2.19.1-r0
- opensearch-2-cross-cluster-replication< 2.19.1-r0
- opensearch-2-crypto-kms< 2.19.1-r0
- opensearch-2-custom-codecs< 2.19.1-r0
- opensearch-2-discovery-azure-classic< 2.19.1-r0
- opensearch-2-discovery-ec2< 2.19.1-r0
- opensearch-2-discovery-gce< 2.19.1-r0
- opensearch-2-entrypoint-compat< 2.19.1-r0
- opensearch-2-geospatial< 2.19.1-r0
- opensearch-2-identity-shiro< 2.19.1-r0
- opensearch-2-index-management< 2.19.1-r0
- opensearch-2-ingest-attachment< 2.19.1-r0
- opensearch-2-job-scheduler< 2.19.1-r0
- opensearch-2-jre-bcfips< 2.19.1-r0
- opensearch-2-jre-bcfips-alerting< 2.19.1-r0
- opensearch-2-jre-bcfips-analysis-icu< 2.19.1-r0
- opensearch-2-jre-bcfips-analysis-kuromoji< 2.19.1-r0
- opensearch-2-jre-bcfips-analysis-nori< 2.19.1-r0
- opensearch-2-jre-bcfips-analysis-phonetic< 2.19.1-r0
- opensearch-2-jre-bcfips-analysis-smartcn< 2.19.1-r0
- opensearch-2-jre-bcfips-analysis-stempel< 2.19.1-r0
- opensearch-2-jre-bcfips-analysis-ukrainian< 2.19.1-r0
- opensearch-2-jre-bcfips-anomaly-detection< 2.19.1-r0
- opensearch-2-jre-bcfips-asynchronous-search< 2.19.1-r0
- opensearch-2-jre-bcfips-cross-cluster-replication< 2.19.1-r0
- opensearch-2-jre-bcfips-crypto-kms< 2.19.1-r0
- opensearch-2-jre-bcfips-custom-codecs< 2.19.1-r0
- opensearch-2-jre-bcfips-discovery-azure-classic< 2.19.1-r0
- opensearch-2-jre-bcfips-discovery-ec2< 2.19.1-r0
- opensearch-2-jre-bcfips-discovery-gce< 2.19.1-r0
- opensearch-2-jre-bcfips-geospatial< 2.19.1-r0
- opensearch-2-jre-bcfips-identity-shiro< 2.19.1-r0
- opensearch-2-jre-bcfips-index-management< 2.19.1-r0
- opensearch-2-jre-bcfips-ingest-attachment< 2.19.1-r0
- opensearch-2-jre-bcfips-job-scheduler< 2.19.1-r0
- opensearch-2-jre-bcfips-k-nn< 2.19.1-r0
- opensearch-2-jre-bcfips-mapper-annotated-text< 2.19.1-r0
- opensearch-2-jre-bcfips-mapper-murmur3< 2.19.1-r0
- opensearch-2-jre-bcfips-mapper-size< 2.19.1-r0
- opensearch-2-jre-bcfips-ml-commons< 2.19.1-r0
- opensearch-2-jre-bcfips-neural-search< 2.19.1-r0
- opensearch-2-jre-bcfips-notifications< 2.19.1-r0
- opensearch-2-jre-bcfips-observability< 2.19.1-r0
- opensearch-2-jre-bcfips-performance-analyzer< 2.19.1-r0
- opensearch-2-jre-bcfips-reporting< 2.19.1-r0
- opensearch-2-jre-bcfips-repository-azure< 2.19.1-r0
- opensearch-2-jre-bcfips-repository-gcs< 2.19.1-r0
- opensearch-2-jre-bcfips-repository-s3< 2.19.1-r0
- opensearch-2-jre-bcfips-security< 2.19.1-r0
- opensearch-2-jre-bcfips-security-analytics< 2.19.1-r0
- opensearch-2-jre-bcfips-sql< 2.19.1-r0
- opensearch-2-jre-bcfips-store-smb< 2.19.1-r0
- opensearch-2-jre-bcfips-telemetry-otel< 2.19.1-r0
- opensearch-2-jre-bcfips-transport-nio< 2.19.1-r0
- opensearch-2-k-nn< 2.19.1-r0
- opensearch-2-mapper-annotated-text< 2.19.1-r0
- opensearch-2-mapper-murmur3< 2.19.1-r0
- opensearch-2-mapper-size< 2.19.1-r0
- opensearch-2-ml-commons< 2.19.1-r0
- opensearch-2-neural-search< 2.19.1-r0
- opensearch-2-notifications< 2.19.1-r0
- opensearch-2-observability< 2.19.1-r0
- opensearch-2-performance-analyzer< 2.19.1-r0
- opensearch-2-reporting< 2.19.1-r0
- opensearch-2-repository-azure< 2.19.1-r0
- opensearch-2-repository-gcs< 2.19.1-r0
- opensearch-2-repository-s3< 2.19.1-r0
- opensearch-2-security< 2.19.1-r0
- opensearch-2-security-analytics< 2.19.1-r0
- opensearch-2-sql< 2.19.1-r0
- opensearch-2-store-smb< 2.19.1-r0
- opensearch-2-telemetry-otel< 2.19.1-r0
- opensearch-2-transport-nio< 2.19.1-r0
Wolfi41 products
- opensearch-2< 2.19.1-r0
- opensearch-2-alerting< 2.19.1-r0
- opensearch-2-analysis-icu< 2.19.1-r0
- opensearch-2-analysis-kuromoji< 2.19.1-r0
- opensearch-2-analysis-nori< 2.19.1-r0
- opensearch-2-analysis-phonetic< 2.19.1-r0
- opensearch-2-analysis-smartcn< 2.19.1-r0
- opensearch-2-analysis-stempel< 2.19.1-r0
- opensearch-2-analysis-ukrainian< 2.19.1-r0
- opensearch-2-anomaly-detection< 2.19.1-r0
- opensearch-2-asynchronous-search< 2.19.1-r0
- opensearch-2-cross-cluster-replication< 2.19.1-r0
- opensearch-2-crypto-kms< 2.19.1-r0
- opensearch-2-custom-codecs< 2.19.1-r0
- opensearch-2-discovery-azure-classic< 2.19.1-r0
- opensearch-2-discovery-ec2< 2.19.1-r0
- opensearch-2-discovery-gce< 2.19.1-r0
- opensearch-2-geospatial< 2.19.1-r0
- opensearch-2-identity-shiro< 2.19.1-r0
- opensearch-2-index-management< 2.19.1-r0
- opensearch-2-ingest-attachment< 2.19.1-r0
- opensearch-2-job-scheduler< 2.19.1-r0
- opensearch-2-k-nn< 2.19.1-r0
- opensearch-2-mapper-annotated-text< 2.19.1-r0
- opensearch-2-mapper-murmur3< 2.19.1-r0
- opensearch-2-mapper-size< 2.19.1-r0
- opensearch-2-ml-commons< 2.19.1-r0
- opensearch-2-neural-search< 2.19.1-r0
- opensearch-2-notifications< 2.19.1-r0
- opensearch-2-observability< 2.19.1-r0
- opensearch-2-performance-analyzer< 2.19.1-r0
- opensearch-2-reporting< 2.19.1-r0
- opensearch-2-repository-azure< 2.19.1-r0
- opensearch-2-repository-gcs< 2.19.1-r0
- opensearch-2-repository-s3< 2.19.1-r0
- opensearch-2-security< 2.19.1-r0
- opensearch-2-security-analytics< 2.19.1-r0
- opensearch-2-sql< 2.19.1-r0
- opensearch-2-store-smb< 2.19.1-r0
- opensearch-2-telemetry-otel< 2.19.1-r0
- opensearch-2-transport-nio< 2.19.1-r0
2 vendors · 124 products
References
0 linksNo references have been published for this record.
Related vulnerabilities
CVE-2025-54988apache software foundationapache tika pdf parser module+6748.52%Critical XXE in Apache Tika (tika-parser-pdf-module) in Apache Tika 1.13 through and including 3.2.1 on all platforms allows an attacker to carry out XML External Entity injection via a crafted XFA file inside of a PDF. An attacker may be able to read sensitive data or trigger malicious requests to internal resources or third-party servers. Note that the tika-parser-pdf-module is used as a dependency in several Tika packages including at least: tika-parsers-standard-modules, tika-parsers-standard-package, tika-app, tika-grpc and tika-server-standard.
Users are recommended to upgrade to version 3.2.2, which fixes this issue.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-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.CVE-2025-0851chainguardopensearch-2+4423.27%A path traversal issue in ZipUtils.unzip and TarUtils.untar in Deep Java Library (DJL) on all platforms allows a bad actor to write files to arbitrary locations.CVE-2025-9624amazonopensearch+460.68%A vulnerability in OpenSearch allows attackers to cause Denial of Service (DoS) by submitting complex query_string inputs.
This issue affects all OpenSearch versions between 3.0.0 and < 3.3.0 and OpenSearch < 2.19.4.CVE-2025-31672apache software foundationapache poi+511.35%Improper Input Validation vulnerability in Apache POI. The issue affects the parsing of OOXML format files like xlsx, docx and pptx. These file formats are basically zip files and it is possible for malicious users to add zip entries with duplicate names (including the path) in the zip. In this case, products reading the affected file could read different data because 1 of the zip entries with the duplicate name is selected over another but different products may choose a different zip entry.
This issue affects Apache POI poi-ooxml before 5.4.0. poi-ooxml 5.4.0 has a check that throws an exception if zip entries with duplicate file names are found in the input file.
Users are recommended to upgrade to version poi-ooxml 5.4.0, which fixes the issue. Please read https://poi.apache.org/security.html for recommendations about how to use the POI libraries securely.