Apache Camel information exposure vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.3 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2023-34442: 0.43% estimated exploitation activity in the next 30 days; percentile 37.06 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Software Foundation Apache Camel. This issue affects Apache Camel from 3.X through <=3.14.8, from 3.18.X through <=3.18.7, from 3.20.X through <= 3.20.5, from 4.X through <= 4.0.0-M3. Users should upgrade to 3.14.9, 3.18.8, 3.20.6 or 3.21.0 and for users on Camel 4.x update to 4.0.0-RC1

Published by the source

10 Jul 2023, 18:30 UTC

Last modified by the source

6 Nov 2023, 05:05 UTC

Source last checked

26 Oct 2026, 16:16 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6g2w-257v-3c9f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-34442

Advisory: Apache Camel information exposure vulnerability
IDs: CVE-2023-34442, GHSA-6g2w-257v-3c9f
Record: https://patchnext.com/advisories/cve-2023-34442 (revision 1, source checked 26 Oct 2026, 16:16 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.camel:camel-jira 4.0.0-RC1, 3.20.6, 3.18.8, 3.14.9. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.camel:camel-jira: affected >= 3.0.0-M3, < 3.14.9; >= 3.15.0, < 3.18.8; >= 3.20.0, < 3.20.6; >= 4.0.0-M1, <= 4.0.0-M3; fixed in 3.18.8, 3.14.9, 3.20.6, 4.0.0-RC1

## Suggested inspection (read-only)
- Maven org.apache.camel:camel-jira: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.camel:camel-jira.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6g2w-257v-3c9f (GitHub-reviewed advisory GHSA-6g2w-257v-3c9f lists affected ranges: Maven org.apache.camel:camel-jira >=3.0.0-M3 =3.15.0 =3.20.0 =4.0.0-M1 <=4.0.0-M3)

Commands are suggestions: review each one before running it.