nday
CVE-2026-85243

Apache Camel: Camel-Crypto-PGP Integrity Verification Downgrade via Attacker-Controlled Message Structure

Apache Software Foundation / Apache Camel

CVE 레코드 공개보다 1일 앞서 기술 분석 게재. nday가 아직 패치 근거를 수집하지 않았습니다. 패치가 없다는 뜻은 아닙니다. PoC 출처 4곳 모두 미등재. CISA KEV 미등재.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

remote, unauthenticated
AV:N, PR:N, UI:N in CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N (CVSS 3.1) from the CNA apache
network
AV:N in CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N (CVSS 3.1) from the CNA apache
no authentication required
PR:N in CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N (CVSS 3.1) from the CNA apache
no user interaction
UI:N in CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N (CVSS 3.1) from the CNA apache
현재 단계
ANA
공개
CVSS
5.9 MEDIUM v3.1

생명주기

가로축 UTC. 점 = 분 단위, 넓은 막대 = 날짜만, 빈 표시 = 불명 또는 추정.
시점 알 수 없음
DIS공개
10-19T10:32Z
PAT패치
아직 기록 없음
ANA분석
10-18T13:01Z
POCPoC
아직 기록 없음
ITW악용
아직 기록 없음
KEVKEV
아직 기록 없음

요약

Improper Validation of Integrity Check Value vulnerability in Apache Camel Crypto PGP component.

This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.

unmarshal() verified the modification detection code only when the message was an OpenPGP symmetrically encrypted integrity protected data packet. The older symmetrically encrypted data packet carries no such code, and OpenPGP's CFB mode is malleable without one, so a message using that packet skipped the check altogether. The packet type is chosen by whoever produced the message, which left the sender - or anyone able to rewrite the message in transit - deciding whether the integrity check applied at all. The existing integrity option governs marshalling only and had no decrypt-side counterpart, so a deployment could not require integrity protection on the messages it accepted.

Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. A requireIntegrityProtection option, defaulting to true, now rejects a message that is not integrity protected. Note that signatureVerificationOption still defaults to optional, so a message carrying no signature is accepted; the two options together are what give a decrypted message authenticity and not only confidentiality. For deployments that cannot upgrade immediately, reject messages that do not use the integrity protected packet before they reach the data format. Routes that must interoperate with a sender still emitting the legacy packet should set requireIntegrityProtection=false after upgrading, and treat the decrypted content as unauthenticated.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:H
High: success depends on conditions outside the attacker's control, such as gathering details of the target or winning a race
Privileges required PR:N
None: no account or authorization needed
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

CVSS 3.1 vector from the CVE record, scored by the CNA apache.

이벤트 로그

+ANA기술 분석

oss-security 메일링 리스트에 게시: “Apache Camel: 38 CVEs fixed in 4.18.5, 4.22.1 and 4.23.0”.

출처 osssec 2026/q4/222 · nday 실시간 관측 · 원본
{
  "id": 495574,
  "type": "analysis_published",
  "source": "osssec",
  "url": "https://seclists.org/oss-sec/2026/q4/222",
  "occurred_at": "2026-10-18T13:01:30Z",
  "observed_at": "2026-11-20T08:13:28.642196Z",
  "is_backfill": false,
  "dedupe_key": "2026/q4/222",
  "detail": {
    "list": "oss-security",
    "author": "Andrea Cosentino",
    "subject": "Apache Camel: 38 CVEs fixed in 4.18.5, 4.22.1 and 4.23.0",
    "is_reply": false
  }
}
+DISCVE 공개

CVE 레코드 공개(CNA: apache). CVSS 5.9(중간).

출처 cvelist · nday 일괄 수집 · 원본
{
  "id": 449615,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-85243",
  "occurred_at": "2026-10-19T10:32:21.246Z",
  "observed_at": "2026-11-13T05:40:13.149746Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N",
      "version": "3.1",
      "base_score": 5.9,
      "base_severity": "MEDIUM"
    },
    "ssvc": {
      "timestamp": "2026-10-19T18:34:06.410581Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "partial"
    },
    "state": "PUBLISHED",
    "date_published": "2026-10-19T10:32:21.246Z",
    "assigner_short_name": "apache"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

연구자 논의

최근 7일간 연구자 0명이 언급

목록의 연구자가 X에서 이 CVE를 언급한 게시물입니다. 원문 그대로 보여 주며 nday는 검증하지 않습니다.

명단의 연구자가 X에서 이 CVE를 언급한 게시물은 아직 수집되지 않았습니다.

Discussion

0 comments

No comments yet.