CVE Intelligence
Medium

CVE-2026-85316 — Apache Camel: Camel-Platform-HTTP Unintended Proxy Mode via Prefix Path Matching

Insufficient Granularity of Access Control vulnerability in Apache Camel Platform HTTP component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. The component decided whether an endpoint ran in proxy mode by testing whether its configured path started with the string proxy, rather than by matching the path exactly. Any endpoint whose path merely begins with those characters - proxyStatus, proxy-config, proxying and so on - therefore became a proxy endpoint without the route author asking for it. A proxy endpoint forwards requests onward, so an endpoint that was intended to serve its own content instead relays traffic on behalf of whoever calls it, which is both a request forgery primitive and an exposure of whatever the forwarding path can reach. 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. Proxy mode is now selected by an exact path match rather than by prefix. For deployments that cannot upgrade immediately, rename any endpoint path that begins with proxy but is not intended to be a proxy.

Published Oct 19, 2026 · Updated Oct 21, 2026 · Sources: CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database · 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.3% (30-day exploitation probability)+3
  • Technical severity (medium)+3

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.3%
ahead of 21% of scored CVEs · Oct 23, 2026
Affects
Apache Software Foundation
Camel
CVSS base
4.8
Medium · 2 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.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

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).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Apache Software Foundation Camel ≥ 4.0.0 and < 4.18.5≥ 4.19.0 and < 4.22.1 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

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

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

Every base score collected

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

ScoreVersionSeverityExpl.ImpactScored by
4.8 CVSS 3.1 Medium 2.2 2.5 security@apache.org via NIST National Vulnerability Database
4.8 CVSS 3.1 Medium — — apache via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N (score shown at the top: security@apache.org)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-1220

Other CVEs with this weakness →

EPSS over time FIRST

Oct 20, 2026 → Oct 23, 2026 · 4 reading(s) · max 0.30%

Detection

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

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Awaiting Analysis → Undergoing Analysis
    Oct 21, 2026 · NIST National Vulnerability Database
  • Source status changed · Received → Awaiting Analysis
    Oct 19, 2026 · NIST National Vulnerability Database
  • SSVC assessment updated
    Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · Published → Received
    Oct 19, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 19, 2026
  • CVSS changed · 4.8
    Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
  • Record created in this database
    Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
  • CVE published
    Oct 19, 2026 · apache

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 19, 2026 – Oct 19, 2026

References

5 on the record

Elsewhere on this site

Apache Software Foundation
every CVE for this vendor
CWE-1220
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-88900 Apache Camel: Camel-JGroups: Unsafe Java Deserialization of Cluster Messages in the JGroups Consumer Can Lead to Remote Code Execution 5d
  • CVE-2026-91858 Apache Camel: Camel-FOP Resolves External DTDs and Entities From Untrusted XSL-FO Input When a Third-Party JAXP TransformerFactory Is Present 5d
  • CVE-2026-88901 Apache Camel: Camel-Smooks XML External Entity Processing, external entities resolved by default 5d
  • CVE-2026-85317 Apache Camel: Camel-HTTP OAuth2 Token Confusion via an Under-Keyed JVM-Global Token Cache 5d
  • CVE-2026-85313 Apache Camel: Camel-Jetty Cross-Origin Credential Exposure via Allow-All CrossOriginFilter Defaults When enableCORS Is Set 5d
  • CVE-2026-85314 Apache Camel: Camel-Mail Header Injection via Unfiltered mail.smtp Headers in the MimeMultipart Data Format (Incomplete Fix of CVE-2026-46584) 5d

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 fixed version, patch or mitigation documented.
  • 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-2026-85316 is "Apache Camel: Camel-Platform-HTTP Unintended Proxy Mode via Prefix Path Matching", rated Medium. 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 4.8 describes technical severity. EPSS 0.30% 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.