{"items":[{"id":"NVI-00013947","kind":"vulnerability","title":"Apache Camel-Azure-Storage-DataLake: the downloadToFile operation built the local download target from the remote path name without constraining it to the configured fileDir","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-7jwc-q3fj-c9pq","CVE-2026-60093"],"plain_summary":"GitHub lists this reviewed advisory for org.apache.camel:camel-azure-storage-datalake, org.apache.camel:camel-azure-storage-datalake, org.apache.camel:camel-azure-storage-datalake. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-12a88482ae8d389aafa9a4e535e22179"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-08-28T20:29:24.000Z","value":"5.5 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-238457e806db3f171adcd28cc51e4de9"},{"kind":"CVSS","as_of":"2026-10-12T15:10:00.207Z","value":"5.5 MEDIUM (3.1)","meaning":"134c704f-9b21-4f2e-91b3-4a467353bcc0 severity; no combined Null risk score.","source_id":"sr-1503e57ad902c4e55207cb3f0c129e73"},{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"0.237%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.14796. Missing scores are unknown.","source_id":"sr-12a88482ae8d389aafa9a4e535e22179"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-238457e806db3f171adcd28cc51e4de9","url":"https://github.com/advisories/GHSA-7jwc-q3fj-c9pq","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-7jwc-q3fj-c9pq","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T02:21:58.521Z"},{"id":"sr-1503e57ad902c4e55207cb3f0c129e73","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-60093","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-60093","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-08T15:05:24.474Z"},{"id":"sr-12a88482ae8d389aafa9a4e535e22179","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-60093","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:44:07.789Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-238457e806db3f171adcd28cc51e4de9"],"technology":"org.apache.camel:camel-azure-storage-datalake","known_exclusions":[],"conditions_summary":"Relative path traversal vulnerability in Apache Camel Azure-Storage Datalake component\n\nThis issue affects Apache Camel: from 4.0.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0.\n\nThe camel-azure-storage-datalake component can download an Azure Data Lake Storage Gen2 file to the local filesystem through its downloadToFile operation, writing into the directory named by the fileDir endpoint option. DataLakeFileOperations.downloadToFile built the local target by joining fileDir with the remote path name exactly as the Azure SDK reported it (new File(fileDir, fileClientWrapper.getFileName())) and passed the result straight to the SDK download call, with no lexical normalization and no check that the resolved location stayed inside fileDir. The remote name is not route-controlled data: the consumer enumerates the filesystem in DataLakeConsumer.createBatchExchangesFromPath, which lists paths and creates one exchange per entry from PathItem.getName() verbatim, applying no name filtering by default. A path name containing parent-directory segments therefore resolved to a location outside the configured fileDir, letting anyone able to influence the names present in the","public_affected_ranges":[">= 4.0.0, < 4.14.9"]},{"certainty":"source_listed","source_ids":["sr-238457e806db3f171adcd28cc51e4de9"],"technology":"org.apache.camel:camel-azure-storage-datalake","known_exclusions":[],"conditions_summary":"Relative path traversal vulnerability in Apache Camel Azure-Storage Datalake component\n\nThis issue affects Apache Camel: from 4.0.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0.\n\nThe camel-azure-storage-datalake component can download an Azure Data Lake Storage Gen2 file to the local filesystem through its downloadToFile operation, writing into the directory named by the fileDir endpoint option. DataLakeFileOperations.downloadToFile built the local target by joining fileDir with the remote path name exactly as the Azure SDK reported it (new File(fileDir, fileClientWrapper.getFileName())) and passed the result straight to the SDK download call, with no lexical normalization and no check that the resolved location stayed inside fileDir. The remote name is not route-controlled data: the consumer enumerates the filesystem in DataLakeConsumer.createBatchExchangesFromPath, which lists paths and creates one exchange per entry from PathItem.getName() verbatim, applying no name filtering by default. A path name containing parent-directory segments therefore resolved to a location outside the configured fileDir, letting anyone able to influence the names present in the","public_affected_ranges":[">= 4.15.0, < 4.18.4"]},{"certainty":"source_listed","source_ids":["sr-238457e806db3f171adcd28cc51e4de9"],"technology":"org.apache.camel:camel-azure-storage-datalake","known_exclusions":[],"conditions_summary":"Relative path traversal vulnerability in Apache Camel Azure-Storage Datalake component\n\nThis issue affects Apache Camel: from 4.0.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0.\n\nThe camel-azure-storage-datalake component can download an Azure Data Lake Storage Gen2 file to the local filesystem through its downloadToFile operation, writing into the directory named by the fileDir endpoint option. DataLakeFileOperations.downloadToFile built the local target by joining fileDir with the remote path name exactly as the Azure SDK reported it (new File(fileDir, fileClientWrapper.getFileName())) and passed the result straight to the SDK download call, with no lexical normalization and no check that the resolved location stayed inside fileDir. The remote name is not route-controlled data: the consumer enumerates the filesystem in DataLakeConsumer.createBatchExchangesFromPath, which lists paths and creates one exchange per entry from PathItem.getName() verbatim, applying no name filtering by default. A path name containing parent-directory segments therefore resolved to a location outside the configured fileDir, letting anyone able to influence the names present in the","public_affected_ranges":[">= 4.19.0, < 4.22.0"]}],"null_published_at":"2026-11-08T19:53:44.027Z","source_updated_at":"2026-08-28T20:29:24.000Z","source_disclosed_at":"2026-08-24T18:31:51.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-11-02T02:21:58.521Z"},{"id":"NVI-00013947","kind":"vulnerability","title":"Apache Camel-Azure-Storage-DataLake: the downloadToFile operation built the local download target from the remote path name without constraining it to the configured fileDir","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-7jwc-q3fj-c9pq","CVE-2026-60093"],"plain_summary":"GitHub lists this reviewed advisory for org.apache.camel:camel-azure-storage-datalake, org.apache.camel:camel-azure-storage-datalake, org.apache.camel:camel-azure-storage-datalake. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-12a88482ae8d389aafa9a4e535e22179"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-08-28T20:29:24.000Z","value":"5.5 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-238457e806db3f171adcd28cc51e4de9"},{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"0.237%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.14796. Missing scores are unknown.","source_id":"sr-12a88482ae8d389aafa9a4e535e22179"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-238457e806db3f171adcd28cc51e4de9","url":"https://github.com/advisories/GHSA-7jwc-q3fj-c9pq","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-7jwc-q3fj-c9pq","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T02:21:58.521Z"},{"id":"sr-12a88482ae8d389aafa9a4e535e22179","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-60093","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:44:07.789Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-238457e806db3f171adcd28cc51e4de9"],"technology":"org.apache.camel:camel-azure-storage-datalake","known_exclusions":[],"conditions_summary":"Relative path traversal vulnerability in Apache Camel Azure-Storage Datalake component\n\nThis issue affects Apache Camel: from 4.0.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0.\n\nThe camel-azure-storage-datalake component can download an Azure Data Lake Storage Gen2 file to the local filesystem through its downloadToFile operation, writing into the directory named by the fileDir endpoint option. DataLakeFileOperations.downloadToFile built the local target by joining fileDir with the remote path name exactly as the Azure SDK reported it (new File(fileDir, fileClientWrapper.getFileName())) and passed the result straight to the SDK download call, with no lexical normalization and no check that the resolved location stayed inside fileDir. The remote name is not route-controlled data: the consumer enumerates the filesystem in DataLakeConsumer.createBatchExchangesFromPath, which lists paths and creates one exchange per entry from PathItem.getName() verbatim, applying no name filtering by default. A path name containing parent-directory segments therefore resolved to a location outside the configured fileDir, letting anyone able to influence the names present in the","public_affected_ranges":[">= 4.0.0, < 4.14.9"]},{"certainty":"source_listed","source_ids":["sr-238457e806db3f171adcd28cc51e4de9"],"technology":"org.apache.camel:camel-azure-storage-datalake","known_exclusions":[],"conditions_summary":"Relative path traversal vulnerability in Apache Camel Azure-Storage Datalake component\n\nThis issue affects Apache Camel: from 4.0.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0.\n\nThe camel-azure-storage-datalake component can download an Azure Data Lake Storage Gen2 file to the local filesystem through its downloadToFile operation, writing into the directory named by the fileDir endpoint option. DataLakeFileOperations.downloadToFile built the local target by joining fileDir with the remote path name exactly as the Azure SDK reported it (new File(fileDir, fileClientWrapper.getFileName())) and passed the result straight to the SDK download call, with no lexical normalization and no check that the resolved location stayed inside fileDir. The remote name is not route-controlled data: the consumer enumerates the filesystem in DataLakeConsumer.createBatchExchangesFromPath, which lists paths and creates one exchange per entry from PathItem.getName() verbatim, applying no name filtering by default. A path name containing parent-directory segments therefore resolved to a location outside the configured fileDir, letting anyone able to influence the names present in the","public_affected_ranges":[">= 4.15.0, < 4.18.4"]},{"certainty":"source_listed","source_ids":["sr-238457e806db3f171adcd28cc51e4de9"],"technology":"org.apache.camel:camel-azure-storage-datalake","known_exclusions":[],"conditions_summary":"Relative path traversal vulnerability in Apache Camel Azure-Storage Datalake component\n\nThis issue affects Apache Camel: from 4.0.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0.\n\nThe camel-azure-storage-datalake component can download an Azure Data Lake Storage Gen2 file to the local filesystem through its downloadToFile operation, writing into the directory named by the fileDir endpoint option. DataLakeFileOperations.downloadToFile built the local target by joining fileDir with the remote path name exactly as the Azure SDK reported it (new File(fileDir, fileClientWrapper.getFileName())) and passed the result straight to the SDK download call, with no lexical normalization and no check that the resolved location stayed inside fileDir. The remote name is not route-controlled data: the consumer enumerates the filesystem in DataLakeConsumer.createBatchExchangesFromPath, which lists paths and creates one exchange per entry from PathItem.getName() verbatim, applying no name filtering by default. A path name containing parent-directory segments therefore resolved to a location outside the configured fileDir, letting anyone able to influence the names present in the","public_affected_ranges":[">= 4.19.0, < 4.22.0"]}],"null_published_at":"2026-11-06T00:29:57.314Z","source_updated_at":"2026-08-28T20:29:24.000Z","source_disclosed_at":"2026-08-24T18:31:51.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-11-02T02:21:58.521Z"},{"id":"NVI-00013947","kind":"vulnerability","title":"Apache Camel-Azure-Storage-DataLake: the downloadToFile operation built the local download target from the remote path name without constraining it to the configured fileDir","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-7jwc-q3fj-c9pq","CVE-2026-60093"],"plain_summary":"GitHub lists this reviewed advisory for org.apache.camel:camel-azure-storage-datalake, org.apache.camel:camel-azure-storage-datalake, org.apache.camel:camel-azure-storage-datalake. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-238457e806db3f171adcd28cc51e4de9"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-08-28T20:29:24.000Z","value":"5.5 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-238457e806db3f171adcd28cc51e4de9"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-238457e806db3f171adcd28cc51e4de9","url":"https://github.com/advisories/GHSA-7jwc-q3fj-c9pq","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-7jwc-q3fj-c9pq","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T02:21:58.521Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-238457e806db3f171adcd28cc51e4de9"],"technology":"org.apache.camel:camel-azure-storage-datalake","known_exclusions":[],"conditions_summary":"Relative path traversal vulnerability in Apache Camel Azure-Storage Datalake component\n\nThis issue affects Apache Camel: from 4.0.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0.\n\nThe camel-azure-storage-datalake component can download an Azure Data Lake Storage Gen2 file to the local filesystem through its downloadToFile operation, writing into the directory named by the fileDir endpoint option. DataLakeFileOperations.downloadToFile built the local target by joining fileDir with the remote path name exactly as the Azure SDK reported it (new File(fileDir, fileClientWrapper.getFileName())) and passed the result straight to the SDK download call, with no lexical normalization and no check that the resolved location stayed inside fileDir. The remote name is not route-controlled data: the consumer enumerates the filesystem in DataLakeConsumer.createBatchExchangesFromPath, which lists paths and creates one exchange per entry from PathItem.getName() verbatim, applying no name filtering by default. A path name containing parent-directory segments therefore resolved to a location outside the configured fileDir, letting anyone able to influence the names present in the","public_affected_ranges":[">= 4.0.0, < 4.14.9"]},{"certainty":"source_listed","source_ids":["sr-238457e806db3f171adcd28cc51e4de9"],"technology":"org.apache.camel:camel-azure-storage-datalake","known_exclusions":[],"conditions_summary":"Relative path traversal vulnerability in Apache Camel Azure-Storage Datalake component\n\nThis issue affects Apache Camel: from 4.0.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0.\n\nThe camel-azure-storage-datalake component can download an Azure Data Lake Storage Gen2 file to the local filesystem through its downloadToFile operation, writing into the directory named by the fileDir endpoint option. DataLakeFileOperations.downloadToFile built the local target by joining fileDir with the remote path name exactly as the Azure SDK reported it (new File(fileDir, fileClientWrapper.getFileName())) and passed the result straight to the SDK download call, with no lexical normalization and no check that the resolved location stayed inside fileDir. The remote name is not route-controlled data: the consumer enumerates the filesystem in DataLakeConsumer.createBatchExchangesFromPath, which lists paths and creates one exchange per entry from PathItem.getName() verbatim, applying no name filtering by default. A path name containing parent-directory segments therefore resolved to a location outside the configured fileDir, letting anyone able to influence the names present in the","public_affected_ranges":[">= 4.15.0, < 4.18.4"]},{"certainty":"source_listed","source_ids":["sr-238457e806db3f171adcd28cc51e4de9"],"technology":"org.apache.camel:camel-azure-storage-datalake","known_exclusions":[],"conditions_summary":"Relative path traversal vulnerability in Apache Camel Azure-Storage Datalake component\n\nThis issue affects Apache Camel: from 4.0.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0.\n\nThe camel-azure-storage-datalake component can download an Azure Data Lake Storage Gen2 file to the local filesystem through its downloadToFile operation, writing into the directory named by the fileDir endpoint option. DataLakeFileOperations.downloadToFile built the local target by joining fileDir with the remote path name exactly as the Azure SDK reported it (new File(fileDir, fileClientWrapper.getFileName())) and passed the result straight to the SDK download call, with no lexical normalization and no check that the resolved location stayed inside fileDir. The remote name is not route-controlled data: the consumer enumerates the filesystem in DataLakeConsumer.createBatchExchangesFromPath, which lists paths and creates one exchange per entry from PathItem.getName() verbatim, applying no name filtering by default. A path name containing parent-directory segments therefore resolved to a location outside the configured fileDir, letting anyone able to influence the names present in the","public_affected_ranges":[">= 4.19.0, < 4.22.0"]}],"null_published_at":"2026-11-02T10:00:37.190Z","source_updated_at":"2026-08-28T20:29:24.000Z","source_disclosed_at":"2026-08-24T18:31:51.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-02T02:21:58.521Z"}],"next_cursor":null,"snapshot_revision":"42594"}