Skip to main content
Vulnerability Database/CVE-2026-85300

CVE-2026-85300: Apache Camel PQC Information Disclosure

CVE-2026-85300 is an information disclosure flaw in Apache Camel PQC component caused by incorrect file permissions on private key material. This post covers technical details, affected versions, impact, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-85300 Overview

CVE-2026-85300 is an Incorrect Default Permissions vulnerability [CWE-276] in the Apache Camel Post-Quantum Cryptography (PQC) component. The flaw affects Apache Camel versions 4.12.0 through 4.18.4 and 4.19.0 through 4.22.0. When the component writes generated key material to disk, it applies the process default umask rather than restricting the file to its owner. On hosts where the umask permits group or world read access, local accounts can read the private key file.

Critical Impact

A local user with filesystem read access to the key directory can recover the private key, defeating every signature and key exchange the deployment performs with it.

Affected Products

  • Apache Camel 4.12.0 through 4.18.4
  • Apache Camel 4.19.0 through 4.22.0
  • Apache Camel PQC component in the above release streams

Discovery Timeline

  • 2026-10-19 - CVE-2026-85300 published to the National Vulnerability Database
  • 2026-10-19 - Last updated in NVD database

Technical Details for CVE-2026-85300

Vulnerability Analysis

The Apache Camel PQC component generates cryptographic key material used for post-quantum signature and key exchange operations. When persisting that material, the component opens the output file without specifying restrictive file mode bits. The resulting permissions reflect the process umask at runtime. On most Linux distributions the default umask of 0022 produces files readable by group and world, which exposes the private key to any local account that can traverse the directory.

The Apache Camel threat model treats remote senders as the primary adversary, so this local exposure is scored at the lower end of the severity scale. The practical consequence, however, is complete key compromise wherever a non-privileged local user can read the file.

Root Cause

The root cause is reliance on the operating system umask to constrain the permissions of security-sensitive output files. The PQC component did not call an equivalent of Files.setPosixFilePermissions with owner-only bits (rw-------, mode 0600) after creating the key file. See Apache Camel CVE-2026-85300 Advisory and Apache JIRA Issue CAMEL-24447 for the upstream root-cause discussion.

Attack Vector

Exploitation requires local access to the host running Apache Camel and read permission on the directory containing the generated key material. A low-privileged local account enumerates the key directory, reads the private key file created with permissive mode bits, and uses the key to forge signatures or decrypt sessions negotiated with it. No network access, user interaction, or elevated privileges are required beyond standard interactive shell access on the host.

// No verified public exploit code is available for CVE-2026-85300.
// See the Apache Camel advisory and pull requests #25826, #25856, and #25857
// for the authoritative patch and fix details.

Detection Methods for CVE-2026-85300

Indicators of Compromise

  • Private key files generated by the Camel PQC component with world- or group-readable permissions (any mode other than 0600 or 0400).
  • Access events on key files from user accounts that are not the Camel service account.
  • Unexpected signature or key-exchange operations completing successfully from hosts outside the authorized deployment.

Detection Strategies

  • Inventory Apache Camel deployments and flag any instance running 4.12.0–4.18.4 or 4.19.0–4.22.0 with the PQC component enabled.
  • Audit the configured PQC key directory with find <keydir> -type f \! -perm 600 to list files that violate owner-only permissions.
  • Review process umask for the Camel service user; a value other than 0077 on affected versions indicates likely exposure.

Monitoring Recommendations

  • Enable Linux auditd rules on PQC key file paths to log every open and openat event with the invoking UID.
  • Forward filesystem access telemetry to a centralized data lake and alert when non-service accounts read key material.
  • Track Apache Camel version strings in software bill of materials data to identify unpatched hosts over time.

How to Mitigate CVE-2026-85300

Immediate Actions Required

  • Upgrade Apache Camel to 4.23.0, or to the LTS fix releases 4.18.5 or 4.22.1, depending on the active release stream.
  • Treat any key material already written by a vulnerable version as exposed and rotate it, including re-issuing associated certificates.
  • Restrict directory traversal on the PQC key directory to the Camel service account only.

Patch Information

Apache has published fixes that write key material with owner-only permissions. The authoritative references are Apache Camel CVE-2026-85300 Advisory, GitHub Pull Request #25826, GitHub Pull Request #25856, and GitHub Pull Request #25857. Upgrade paths: 4.19.x–4.22.0 users move to 4.22.1; 4.12.0–4.18.4 LTS users move to 4.18.5; all other users move to 4.23.0.

Workarounds

  • Place the PQC key directory on a path that only the Camel service account can traverse, for example parent directory mode 0700 owned by the service user.
  • Tighten the Camel process umask to 0077 so new files are created without group or world access.
  • After tightening permissions, rotate any key material previously written with permissive modes; existing files are not retroactively re-permissioned by the fix.
bash
# Configuration example: restrict umask and key directory for the Camel service
sudo install -d -o camel -g camel -m 0700 /var/lib/camel/pqc-keys

# systemd unit drop-in to enforce a restrictive umask
sudo mkdir -p /etc/systemd/system/camel.service.d
cat <<'EOF' | sudo tee /etc/systemd/system/camel.service.d/umask.conf
[Service]
UMask=0077
EOF
sudo systemctl daemon-reload
sudo systemctl restart camel

# Audit existing key files and rotate any that are not owner-only
sudo find /var/lib/camel/pqc-keys -type f \! -perm 600 -print

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.