CVE-2026-85315: Software Security Vulnerability Vulnerability
MODERATECVE-2026-85315 is a MODERATE (CVSS 5.3) security vulnerability vulnerability (CWE-209: Generation of Error Message Containing Sensitive Information) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product generates an error message that includes sensitive information about its environment, users, or associated data.. Remediation is available in the latest vendor maintenance releases.
CVE-2026-85315 at a Glance
Security Impact
CVSS: 5.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N).
How to Fix CVE-2026-85315
To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-85315, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree
Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.
Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-209: Generation of Error Message Containing Sensitive Information, where the product generates an error message that includes sensitive information about its environment, users, or associated data. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
References
Frequently Asked Questions
What is CVE-2026-85315?
Which Software versions are affected?
What version fixes CVE-2026-85315?
What is the CVSS score of CVE-2026-85315?
What CWE is associated with CVE-2026-85315?
How can I check Maven dependencies for CVE-2026-85315?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-xj93-qh7c-f9w3",
"modified" : "2026-10-19T12:32:52Z",
"published" : "2026-10-19T12:32:52Z",
"aliases" : [ "CVE-2026-85315" ],
"details" : "Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel gRPC component.\n\nThis issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.\n\nWhen a route behind a gRPC consumer failed, the exception's message was placed into the gRPC status description. Unlike the status cause, which stays local to the server, the description is transmitted to the calling client, so an external caller able to provoke a failure could read the internal error message. What that discloses depends on the exception, and in practice includes class and package names, paths, host names and connection detail carried in messages. This is the gRPC member of the same unmuted-consumer-exception family as the knative, mina and CXF advisories published alongside it.\n\nUpgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. A muteException consumer option, defaulting to true, puts a generic description in the status instead of the route exception's message. Set muteException=false to restore the previous output. For deployments that cannot upgrade immediately, map failures onto an explicit status in an onException handler so the framework never copies the exception message into the description.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N"
} ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-85315"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/pull/25839"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/pull/25934"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/pull/25935"
}, {
"type" : "WEB",
"url" : "https://camel.apache.org/security/CVE-2026-85315.html"
}, {
"type" : "WEB",
"url" : "https://issues.apache.org/jira/browse/CAMEL-24478"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-209" ],
"severity" : "MODERATE",
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-10-19T11:17:24Z"
}
}