CVE-2026-85245: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-ww26-c733-j3r5
CVSS 5.9
CWE-488
Published
Advisory Summary

CVE-2026-85245 is a MODERATE (CVSS 5.9) security vulnerability vulnerability (CWE-488: Exposure of Data Element to Wrong Session) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product does not sufficiently enforce boundaries between the states of different sessions, causing data to be provided to, or used by, the wrong session.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-85245 at a Glance

CVE Identifier CVE-2026-85245
GHSA Identifier GHSA-ww26-c733-j3r5
Severity MODERATE
CVSS v3.1 Base Score 5.9
CWE Classification CWE-488: Exposure of Data Element to Wrong Session
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.9

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-85245

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.

Verify Direct and Transitive Dependencies

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-85245, 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-488: Exposure of Data Element to Wrong Session, where the product does not sufficiently enforce boundaries between the states of different sessions, causing data to be provided to, or used by, the wrong session. 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

Exposure of Data Element to Wrong Session vulnerability in Apache Camel Thrift component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. The Thrift data format unmarshalled incoming data into the shared defaultInstance of the target type rather than into a fresh copy, and returned that shared object as the exchange body. Because the instance is shared process-wide, state written while unmarshalling one message stayed on the object and was visible to every later message that used the same type. Fields absent from a later payload retained the previous message's values, so content belonging to one sender could be read while processing another sender's message, and concurrent exchanges could observe each other's partially written state. In a deployment that serves more than one tenant or user through the same route, that is disclosure of one party's data to another. Upgrade 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. Unmarshalling now deserializes into a copy, so each exchange gets its own instance and no state carries between messages. For deployments that cannot upgrade immediately, copy the unmarshalled body into a new instance immediately after the data format runs, and do not retain references to the returned object.

References

Frequently Asked Questions

What is CVE-2026-85245?
CVE-2026-85245 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-488: Exposure of Data Element to Wrong Session.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-85245?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-85245?
CVE-2026-85245 has a CVSS v3.1 base score of 5.9 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-85245?
CVE-2026-85245 is classified under CWE-488: Exposure of Data Element to Wrong Session (The product does not sufficiently enforce boundaries between the states of different sessions, causing data to be provided to, or used by, the wrong session.).
How can I check Maven dependencies for CVE-2026-85245?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-ww26-c733-j3r5",
  "modified" : "2026-10-19T12:32:51Z",
  "published" : "2026-10-19T12:32:50Z",
  "aliases" : [ "CVE-2026-85245" ],
  "details" : "Exposure of Data Element to Wrong Session vulnerability in Apache Camel Thrift component.\n\n\n\nThis issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.\n\nThe Thrift data format unmarshalled incoming data into the shared defaultInstance of the target type rather than into a fresh copy, and returned that shared object as the exchange body. Because the instance is shared process-wide, state written while unmarshalling one message stayed on the object and was visible to every later message that used the same type. Fields absent from a later payload retained the previous message's values, so content belonging to one sender could be read while processing another sender's message, and concurrent exchanges could observe each other's partially written state. In a deployment that serves more than one tenant or user through the same route, that is disclosure of one party's data to another.\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. Unmarshalling now deserializes into a copy, so each exchange gets its own instance and no state carries between messages. For deployments that cannot upgrade immediately, copy the unmarshalled body into a new instance immediately after the data format runs, and do not retain references to the returned object.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-85245"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/camel/pull/25823"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/camel/pull/25940"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/camel/pull/25942"
  }, {
    "type" : "WEB",
    "url" : "https://camel.apache.org/security/CVE-2026-85245.html"
  }, {
    "type" : "WEB",
    "url" : "https://issues.apache.org/jira/browse/CAMEL-24442"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-488" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-19T11:17:22Z"
  }
}