Security readout for executives and security teams
Plain-English summary
Apache Camel applications using the LevelDB aggregation repository can be compromised if an attacker can write to that LevelDB store. A crafted serialized Java object may execute code when the application later reads aggregation data. This is serious because successful exploitation can give the attacker the application’s privileges.
Executive priority
Treat as high priority for Camel-based services that use LevelDB aggregation repositories. Prioritize internet-facing or shared-host deployments first, but the key risk is write access to the repository files, not direct unauthenticated network reachability alone.
Technical view
Camel-LevelDB DefaultLevelDBSerializer uses java.io.ObjectInputStream on LevelDB aggregation repository data without ObjectInputFilter or class-loading restrictions. The issue is CWE-502 deserialization of untrusted data and affects Apache Camel 4.10.0 before fixed LTS guidance, 4.14.0 before 4.14.5, and 4.15.0 before 4.18.0.
Likely exposure
Exposure is most likely in Java integration services using org.apache.camel:camel-leveldb for aggregation repositories, especially where LevelDB files are writable by another user, compromised process, shared volume, or deployment pipeline. The source bundle does not prove exposure for Camel deployments that do not use the LevelDB component.
Exploitation context
The bundle lists a public GitHub reference tagged as exploit, but KEV is false and no cited source states active exploitation. Exploitation requires the attacker to write crafted data into LevelDB files used by the Camel application, then wait for normal repository operations to deserialize it.
Researcher notes
The core weakness is unrestricted Java deserialization from a persistence layer. The CVSS vector indicates low-complexity exploitation with low privileges and full confidentiality, integrity, and availability impact. Evidence is incomplete on real-world exploitation and downstream vendor package status beyond the listed references.
Mitigation direction
- Upgrade Apache Camel to 4.18.0 where applicable.
- For 4.10.x LTS, follow vendor guidance to upgrade to 4.10.9.
- For 4.14.x LTS, upgrade to 4.14.5.
- Restrict write access to LevelDB repository files and backing volumes.
- Check Apache and distribution vendor guidance for environment-specific packages.
Validation and detection
- Inventory use of org.apache.camel:camel-leveldb in applications and build manifests.
- Identify Camel versions in the affected 4.10.x, 4.14.x, and 4.15.x ranges.
- Confirm whether LevelDB aggregation repositories are enabled in runtime routes.
- Review filesystem and volume permissions for LevelDB repository paths.
- Check logs and deployment history for unexpected LevelDB file modifications.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-25747 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9CISA-ADPCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-02-23T10:02:59.152Z: Reported to Red Hat.
- 2026-02-23T08:45:45.826Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/oscerd/CVE-2026-25747CVE reference, apache · exploit
- https://camel.apache.org/security/CVE-2026-25747.htmlCVE reference, apache · vendor-advisory
- https://access.redhat.com/security/cve/CVE-2026-25747CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2441910CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-25747.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.