CVE Intelligence
High Insecure deserialization

CVE-2024-22369 — Apache Camel: Camel-SQL: Unsafe Deserialization from JDBCAggregationRepository

Deserialization of Untrusted Data vulnerability in Apache Camel SQL ComponentThis issue affects Apache Camel: from 3.0.0 before 3.21.4, from 3.22.0 before 3.22.1, from 4.0.0 before 4.0.4, from 4.1.0 before 4.4.0. Users are recommended to upgrade to version 4.4.0, which fixes the issue. If users are on the 4.0.x LTS releases stream, then they are suggested to upgrade to 4.0.4. If users are on 3.x, they are suggested to move to 3.21.4 or 3.22.1

Published Feb 20, 2024 · Updated Oct 26, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: apache

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.7% (30-day exploitation probability)+8
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.75%
ahead of 55% of scored CVEs · Oct 29, 2026
Affects
Apache Software Foundation
Camel and 1 more
CVSS base
7.8
High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Maven Org.apache.camel:camel-sql: fixed in version 3.21.4 — github.com (GitHub Security Advisories)
  • Maven Org.apache.camel:camel-sql: fixed in version 3.22.1 — github.com (GitHub Security Advisories)
  • Maven Org.apache.camel:camel-sql: fixed in version 4.0.4 — github.com (GitHub Security Advisories)
  • Maven Org.apache.camel:camel-sql: fixed in version 4.4.0 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Apache Software Foundation Camel, Maven Org.apache.camel:camel-sql).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  4. Search available logs for exploit probes matching the vulnerability class (insecure deserialization), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Apache Software Foundation Camel ≥ 3.0.0 and < 3.21.4≥ 4.0.0 and < 4.0.4≥ 4.1.0 and < 4.4.0version 3.22.0 Vulnerable NIST National Vulnerability Database
Apache Software Foundation Camel ≥ 3.0.0 and < 3.21.4≥ 3.22.0 and < 3.22.1≥ 4.0.0 and < 4.0.4≥ 4.1.0 and < 4.4.0 Vulnerable CVE Program (cve.org) e CISA ADP
Maven Org.apache.camel:camel-sql ≥ 3.0.0 and < 3.21.4≥ 3.22.0 and < 3.22.1≥ 4.0.0 and < 4.0.4≥ 4.1.0 and < 4.4.0 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.8 CVSS 3.1 High 1.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
7.8 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
7.8 CVSS 3.1 High — — CISA-ADP via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (score shown at the top: 134c704f-9b21-4f2e-91b3-4a467353bcc0)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-502 · Deserialization of Untrusted Data

Other CVEs with this weakness →

EPSS over time FIRST

Oct 26, 2026 → Oct 29, 2026 · 4 reading(s) · max 0.75%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Monitor serialized objects in requests and unexpected processes spawned by the runtime.
endpoint telemetry (EDR)application logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 26, 2026 · GitHub Security Advisories
  • Affected products added · maven/org.apache.camel:camel-sql
    Oct 26, 2026 · GitHub Security Advisories
  • Affected products added · apache software foundation/apache camel
    Oct 26, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 26, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 26, 2026
  • Affected products added · apache/camel
    Oct 26, 2026 · NIST National Vulnerability Database
  • CVSS changed · 7.8
    Oct 26, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 26, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 26, 2026 · Alertas do Telegram
  • 2024
  • CVE published
    Feb 20, 2024 · apache

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 26, 2026 – Oct 26, 2026
  • 1× Official description updated · Oct 26, 2026 – Oct 26, 2026

References

14 on the record

Elsewhere on this site

Apache Software Foundation
every CVE for this vendor
Insecure deserialization
same class
CWE-502
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-71569 Apache Camel: Camel-A2A Push Notification Webhook Guard Accepts IPv6 Unique Local Addresses Reached Through a Host Name 1d
  • CVE-2026-94386 Apache Camel: Camel-OAuth Cross-Scope Token Reuse via an Under-Keyed JVM-Global Client Credentials Token Cache 3d
  • CVE-2026-90885 Apache Camel: Camel-Saxon XML External Entity Processing - XQueryBuilder Parsed a Message Body That Was Already a javax.xml.transform.Source With Saxon's Default Parser Settings, so an External Entity Declared in That Body Was Resolved 3d
  • CVE-2026-95664 Apache Camel: Camel-AWS2-S3 Producer Evaluates Untrusted S3 Object Keys From the CamelAwsS3Key Header as Simple Expressions 4d
  • CVE-2026-95663 Apache Camel: Camel-Keycloak Security Policy Accepts Expired Access Tokens Because Cached Token Introspection Results Are Not Bounded by the Token Expiry 4d
  • CVE-2026-95628 Apache Camel: Camel-Docling Custom CLI Argument Path Validation Does Not Reject Absolute Paths (Incomplete Fix of CVE-2026-40047) 4d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2024-22369 is "Apache Camel: Camel-SQL: Unsafe Deserialization from JDBCAggregationRepository", rated High. It affects Camel (Apache Software Foundation); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.75% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.