{ "dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": { "cveId": "CVE-2026-85245", "assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09", "state": "PUBLISHED", "assignerShortName": "apache", "dateReserved": "2026-09-03T16:23:37.430Z", "datePublished": "2026-10-19T10:32:44.450Z", "dateUpdated": "2026-10-19T10:32:44.450Z" }, "containers": { "cna": { "providerMetadata": { "orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09", "shortName": "apache", "dateUpdated": "2026-10-19T10:32:44.450Z" }, "title": "Apache Camel: Camel-Thrift Cross-Exchange Data Disclosure via a Shared Deserialization Target", "problemTypes": [ { "descriptions": [ { "description": "CWE-488 Exposure of Data Element to Wrong Session", "lang": "en", "cweId": "CWE-488", "type": "CWE" } ] } ], "source": { "discovery": "UNKNOWN" }, "affected": [ { "vendor": "Apache Software Foundation", "product": "Apache Camel", "collectionURL": "https://repo.maven.apache.org/maven2", "packageName": "org.apache.camel:camel-thrift", "packageURL": "pkg:maven/org.apache.camel/camel-thrift", "versions": [ { "status": "affected", "version": "4.0.0", "lessThan": "4.18.5", "versionType": "maven" }, { "status": "affected", "version": "4.19.0", "lessThan": "4.22.1", "versionType": "maven" }, { "status": "unaffected", "version": "4.18.5", "versionType": "maven" }, { "status": "unaffected", "version": "4.22.1", "versionType": "maven" }, { "status": "unaffected", "version": "4.23.0", "versionType": "maven" } ], "defaultStatus": "unaffected" } ], "descriptions": [ { "value": "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.", "lang": "en", "supportingMedia": [ { "type": "text/html", "base64": false, "value": "

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": [ { "url": "https://camel.apache.org/security/CVE-2026-85245.html", "name": "Apache Camel Security Advisory - CVE-2026-85245", "tags": [ "vendor-advisory" ] }, { "url": "https://issues.apache.org/jira/browse/CAMEL-24442", "name": "CAMEL-24442", "tags": [ "issue-tracking" ] }, { "url": "https://github.com/apache/camel/pull/25823", "name": "Fix on main, released in 4.23.0 (commit c52d3cfa1c343a49261d77a5213dba92244a38f6)", "tags": [ "patch" ] }, { "url": "https://github.com/apache/camel/pull/25940", "name": "Backport to camel-4.22.x, released in 4.22.1 (commit 260989268cbc6d258b1fcba63770be8ebbec40cb)", "tags": [ "patch" ] }, { "url": "https://github.com/apache/camel/pull/25942", "name": "Backport to camel-4.18.x, released in 4.18.5 (commit af1efbcccf5882b1ef0094db718972da3190e7e9)", "tags": [ "patch" ] } ], "metrics": [ { "scenarios": [ { "lang": "en", "value": "GENERAL" } ], "format": "CVSS", "cvssV3_1": { "version": "3.1", "attackVector": "NETWORK", "attackComplexity": "HIGH", "privilegesRequired": "NONE", "userInteraction": "NONE", "scope": "UNCHANGED", "confidentialityImpact": "HIGH", "integrityImpact": "NONE", "availabilityImpact": "NONE", "baseSeverity": "MEDIUM", "baseScore": 5.9, "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N" } } ], "workarounds": [ { "lang": "en", "value": "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.", "supportingMedia": [ { "type": "text/html", "base64": false, "value": "

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.

" } ] } ], "solutions": [ { "lang": "en", "value": "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.", "supportingMedia": [ { "type": "text/html", "base64": false, "value": "

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.

" } ] } ], "credits": [ { "lang": "en", "value": "Claude Security", "type": "finder" }, { "lang": "en", "value": "Andrea Cosentino", "type": "remediation developer" } ], "x_generator": { "engine": "Vulnogram 1.0.3" } } } }