CGA-3X75-F9J7-7HM9: trino
Unknown
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-3X75-F9J7-7HM9 is a vulnerability in trino with no CVSS score yet.
Priority
Insufficient evidence
No CVSS vector published; no exploitation reported by the 5 checked sources
Source freshness unavailable
How is this decided?CVSS score
Not scored
010
No CVSS score recordedEPSS scoreNot scoredRisk metrics not yet published.
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware 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 catalogs
CISA KEVNot in the CISA KEV catalog.
ENISA CNWNot in the ENISA CNW catalog.
CIRCLNot in the CIRCL catalog.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root causeNo weakness data has been published for this record.
Affected systems
Version check
Known conditions: not stated in public data.
Chainguard49 products
- trino< 439-r0
- trino-config< 439-r0
- trino-oci-entrypoint< 439-r0
- trino-plugin-accumulo< 439-r0
- trino-plugin-atop< 439-r0
- trino-plugin-bigquery< 439-r0
- trino-plugin-blackhole< 439-r0
- trino-plugin-cassandra< 439-r0
- trino-plugin-clickhouse< 439-r0
- trino-plugin-delta-lake< 439-r0
- trino-plugin-druid< 439-r0
- trino-plugin-elasticsearch< 439-r0
- trino-plugin-example-http< 439-r0
- trino-plugin-exchange-filesystem< 439-r0
- trino-plugin-exchange-hdfs< 439-r0
- trino-plugin-geospatial< 439-r0
- trino-plugin-google-sheets< 439-r0
- trino-plugin-hive< 439-r0
- trino-plugin-http-event-listener< 439-r0
- trino-plugin-hudi< 439-r0
- trino-plugin-iceberg< 439-r0
- trino-plugin-ignite< 439-r0
- trino-plugin-jmx< 439-r0
- trino-plugin-kafka< 439-r0
- trino-plugin-kinesis< 439-r0
- trino-plugin-kudu< 439-r0
- trino-plugin-local-file< 439-r0
- trino-plugin-mariadb< 439-r0
- trino-plugin-memory< 439-r0
- trino-plugin-ml< 439-r0
- trino-plugin-mongodb< 439-r0
- trino-plugin-mysql< 439-r0
- trino-plugin-mysql-event-listener< 439-r0
- trino-plugin-oracle< 439-r0
- trino-plugin-password-authenticators< 439-r0
- trino-plugin-pinot< 439-r0
- trino-plugin-postgresql< 439-r0
- trino-plugin-prometheus< 439-r0
- trino-plugin-raptor-legacy< 439-r0
- trino-plugin-redis< 439-r0
- trino-plugin-redshift< 439-r0
- trino-plugin-resource-group-managers< 439-r0
- trino-plugin-session-property-managers< 439-r0
- trino-plugin-singlestore< 439-r0
- trino-plugin-sqlserver< 439-r0
- trino-plugin-teradata-functions< 439-r0
- trino-plugin-thrift< 439-r0
- trino-plugin-tpcds< 439-r0
- trino-plugin-tpch< 439-r0
Wolfi49 products
- trino< 439-r0
- trino-config< 439-r0
- trino-oci-entrypoint< 439-r0
- trino-plugin-accumulo< 439-r0
- trino-plugin-atop< 439-r0
- trino-plugin-bigquery< 439-r0
- trino-plugin-blackhole< 439-r0
- trino-plugin-cassandra< 439-r0
- trino-plugin-clickhouse< 439-r0
- trino-plugin-delta-lake< 439-r0
- trino-plugin-druid< 439-r0
- trino-plugin-elasticsearch< 439-r0
- trino-plugin-example-http< 439-r0
- trino-plugin-exchange-filesystem< 439-r0
- trino-plugin-exchange-hdfs< 439-r0
- trino-plugin-geospatial< 439-r0
- trino-plugin-google-sheets< 439-r0
- trino-plugin-hive< 439-r0
- trino-plugin-http-event-listener< 439-r0
- trino-plugin-hudi< 439-r0
- trino-plugin-iceberg< 439-r0
- trino-plugin-ignite< 439-r0
- trino-plugin-jmx< 439-r0
- trino-plugin-kafka< 439-r0
- trino-plugin-kinesis< 439-r0
- trino-plugin-kudu< 439-r0
- trino-plugin-local-file< 439-r0
- trino-plugin-mariadb< 439-r0
- trino-plugin-memory< 439-r0
- trino-plugin-ml< 439-r0
- trino-plugin-mongodb< 439-r0
- trino-plugin-mysql< 439-r0
- trino-plugin-mysql-event-listener< 439-r0
- trino-plugin-oracle< 439-r0
- trino-plugin-password-authenticators< 439-r0
- trino-plugin-pinot< 439-r0
- trino-plugin-postgresql< 439-r0
- trino-plugin-prometheus< 439-r0
- trino-plugin-raptor-legacy< 439-r0
- trino-plugin-redis< 439-r0
- trino-plugin-redshift< 439-r0
- trino-plugin-resource-group-managers< 439-r0
- trino-plugin-session-property-managers< 439-r0
- trino-plugin-singlestore< 439-r0
- trino-plugin-sqlserver< 439-r0
- trino-plugin-teradata-functions< 439-r0
- trino-plugin-thrift< 439-r0
- trino-plugin-tpcds< 439-r0
- trino-plugin-tpch< 439-r0
2 vendors · 98 products
References
0 linksNo references have been published for this record.
Related vulnerabilities
PrioritiseCVE-2026-91777fasterxml · jackson-databind +701 morejackson-databind: quadratic forward-reference completion in Collection and Map deserializersForward-reference completion for @JsonIdentityInfo object IDs in FasterXML jackson-databind performs a linear scan of the pending-reference accumulator for every resolved ID. The affected paths are CollectionDeserializer.CollectionReferringAccumulator.resolveForwardReference() and the equivalent implementation in MapDeserializer. When a document first creates N unresolved object-ID references in an identity-enabled collection or map and then defines those same IDs in reverse order, completion performs on the order of N * (N + 1) / 2 identity comparisons, so a shallow document whose size grows linearly causes quadratic CPU work during deserialization. The reporter instrumented equals() calls on the ID class and measured exactly 2,003,000 comparisons at N = 2,000, against zero comparisons in the pending-reference lookup path for an equally sized control in which every reference was already resolved. The input requires no deep nesting and no syntactically unusual JSON. Exploitation requires an application that deserializes attacker-influenced JSON into an identity-enabled collection or map. The fix replaces the repeated linear lookup with a keyed pending-reference structure.CVSS7.5HighEPSS0.49%PrioritiseCVE-2026-91776fasterxml · jackson-databind +709 morejackson-databind: unbounded growth of the type id cache in TypeDeserializerBase retains every unknown raw type IDTypeDeserializerBase._findDeserializer() in FasterXML jackson-databind caches the resolved deserializer under the raw, attacker-supplied type ID. When name-based polymorphism is configured with a fallback, for example @JsonTypeInfo(use = Id.NAME, defaultImpl = ...), every distinct unrecognized type ID resolves to the same fallback deserializer but is retained as its own key in the _deserializers map. That map has no configurable bound and lives for the lifetime of the type deserializer, so an attacker who can repeatedly supply fresh unknown type IDs causes monotonic memory retention across requests. The reporter observed 10,000 retained entries from 10,000 distinct unknown IDs, against a single entry for a control that repeated one unknown ID the same number of times, isolating attacker-controlled key cardinality from request volume. Exploitation requires an application that enables name-based polymorphism with a defaultImpl or equivalent fallback, accepts attacker-influenced type IDs, and reuses a long-lived ObjectMapper across requests. The fix stops caching fallback resolutions for unrecognized IDs and bounds both the number of cached entries and the length of a cacheable type ID.CVSS7.5HighEPSS0.49%PrioritiseCVE-2026-68497fasterxml · jackson-databind +603 morejackson-databind: unbounded numeric parse in Duration and XMLGregorianCalendar deserialization allows CPU denial of servicejackson-databind binds a JSON string to a javax.xml.datatype.Duration or javax.xml.datatype.XMLGregorianCalendar field by passing the raw string verbatim to DatatypeFactory.newDuration(value) or newXMLGregorianCalendar(value) in CoreXMLDeserializers.Std._deserialize. These deserializers are registered by default with no opt-in, so a plain ObjectMapper or JsonMapper with no polymorphic typing and no special configuration reaches this path. The XML Schema lexical grammar permits numeric components of arbitrary length, which the JDK materializes through the native BigInteger(String) and BigDecimal(String) constructors, both quadratic in digit count. Because the digits sit inside a JSON string token rather than a JSON number token, jackson-core's StreamReadConstraints.maxNumberLength guard never applies; jackson's own NumberDeserializers call validateIntegerLength or validateFPLength before parsing a stringified number, but the XML datatype deserializer omits that pre-check. An unauthenticated attacker can therefore submit a single request of a few megabytes, such as a Duration value consisting of the letter P followed by several million digits and the letter Y, and force tens of seconds to several minutes of single-threaded CPU work; a handful of concurrent requests can saturate a server's worker threads. This affects com.fasterxml.jackson.core:jackson-databind from 2.0.0 before 2.18.10, from 2.19.0 before 2.21.6, and from 2.22.0 before 2.22.2, and tools.jackson.core:jackson-databind from 3.0.0 before 3.1.6 and from 3.2.0 before 3.2.2. Users should upgrade to 2.18.10, 2.21.6, 2.22.2, 3.1.6, or 3.2.2.CVSS7.5HighEPSS0.63%RoutineCVE-2026-83557fasterxml · jackson-databind +609 morejackson-databind omits java.lang.Comparable from DefaultBaseTypeLimitingValidator's unsafe base typesDefaultBaseTypeLimitingValidator is the PolymorphicTypeValidator applied automatically whenever @JsonTypeInfo is used without an explicitly configured custom validator. It denies polymorphic resolution only for a fixed set of "unsafe base types", and its isSafeSubType method returns true unconditionally for every base type outside that set. java.lang.Comparable was absent from the list despite being implemented by a very large fraction of JDK and application classes, comparable in breadth to java.io.Serializable, which is on the list for that reason. An application declaring an @JsonTypeInfo-annotated property or class with Comparable as its base type, and no custom PolymorphicTypeValidator, will accept a type identifier for essentially any class implementing Comparable. This yields an attacker-controlled object instantiation primitive; a demonstrated case constructs a java.io.File for an arbitrary attacker-chosen path, which becomes path-traversal-adjacent if the application subsequently calls path-sensitive methods on the value. No class implementing Comparable has been identified that yields code execution through deserialization alone. Global Default Typing via activateDefaultTyping is not affected, because that method structurally requires an explicit PolymorphicTypeValidator argument. This affects com.fasterxml.jackson.core:jackson-databind from 2.11.0 before 2.18.10, from 2.19.0 before 2.21.6, and from 2.22.0 before 2.22.2, and tools.jackson.core:jackson-databind from 3.0.0 before 3.1.6 and from 3.2.0 before 3.2.2. Users should upgrade to 2.18.10, 2.21.6, 2.22.2, 3.1.6, or 3.2.2.CVSS5.6MediumEPSS0.72%RoutineCVE-2026-19032fasterxml · jackson-databind +656 morejackson-databind resolves attacker-controlled URI schemes when deserializing java.nio.file.Pathjackson-databind's deserializer for java.nio.file.Path resolves an attacker-supplied URI without restricting the URI scheme. In JDKFromStringDeserializer.NioPathHelper.deserialize, a string bound from untrusted JSON is passed to new URI(value) and then to Path.of(uri). When that throws FileSystemNotFoundException, the code enumerates ServiceLoader<FileSystemProvider> and calls provider.getPath(uri) on the first provider whose scheme matches the attacker-chosen scheme. Untrusted JSON can therefore select and drive an arbitrary registered FileSystemProvider during readValue under a default JsonMapper, and forces provider class loading at the same time. With only the JDK built-in providers (file, jar/zipfs) present, the resolved path is inert and no mount or network I/O occurs; further impact requires a side-effecting third-party FileSystemProvider on the classpath. This affects com.fasterxml.jackson.core:jackson-databind from 2.8.0 before 2.18.10, from 2.19.0 before 2.21.6, and from 2.22.0 before 2.22.2, and tools.jackson.core:jackson-databind from 3.0.0 before 3.1.6 and from 3.2.0 before 3.2.2. Users should upgrade to 2.18.10, 2.21.6, 2.22.2, 3.1.6, or 3.2.2. Binding java.nio.file.Path from untrusted JSON should be avoided regardless of version.CVSS5.3MediumEPSS0.57%PrioritiseCVE-2026-56864go toolchain · cmd/go +1635 moreIgnore unrelated, unauthenticated hashes in Lookup in golang.org/x/mod/sumdbA malicious GOSUMDB was capable of serving arbitrary module content not contained within the transparency log. This attack allows for a coordinating GOPROXY and GOSUMDB to serve a client malicious module content that cannot be detected by evaluating the transparency log. In order to determine if you have been affected: rm -r go.sum go.work.sum vendor/ && go mod tidyCVSS7.5HighEPSS0.30%