NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
LOW severity

Apache Camel information exposure vulnerabilityGHSA-6g2w-257v-3c9f

LOWFix: apache/camel@b61d5b6

GHSA-6g2w-257v-3c9f is a low-severity (CVSS 3.3) Information Exposure vulnerability in org.apache.camel:camel-jira. A fix is available for org.apache.camel:camel-jira — see the affected versions and patch details below.

Also known asCVE-2023-34442
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-6g2w-257v-3c9f.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk
0.00%0.31%0.62%0.93%0.0%0.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected
☕org.apache.camel:camel-jira☕org.apache.camel:camel-jira☕org.apache.camel:camel-jira☕org.apache.camel:camel-jira

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.camel:camel-jira≥ 3.0.0-M3&&< 3.14.93.14.9org.apache.camel:camel-jira:3.14.9
☕Mavenorg.apache.camel:camel-jira≥ 3.15.0&&< 3.18.83.18.8org.apache.camel:camel-jira:3.18.8
☕Mavenorg.apache.camel:camel-jira≥ 3.20.0&&< 3.20.63.20.6org.apache.camel:camel-jira:3.20.6
☕Mavenorg.apache.camel:camel-jira≥ 4.0.0-M1&&< 4.0.0-RC14.0.0-RC1org.apache.camel:camel-jira:4.0.0-RC1

Affected Products

1 product · 6 configurations
Application
camelapache
≥ 3.20.0 && < 3.20.6
1 version
4.0.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.camel:camel-jira, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.apache.camel:camel-jira to 3.14.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6g2w-257v-3c9f is resolved across your whole dependency graph.

  3. Workarounds

    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

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
O3 Security · Impact-Aware SCA

Is GHSA-6g2w-257v-3c9f in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Apache Camel information exposure vulnerability (Low 3.3)