CVE-2026-81320: Red Hat hawtio-operator sensitive information logging

CVE-2026-81320 · Severity: medium · CVSS 5.5 · Published 2026-09-15

The hawtio-operator for Apache Camel logs TLS private keys to standard output when debug logging is enabled. These logs are typically forwarded to centralized systems accessible to anyone with pod log access, potentially exposing encryption keys that attackers could use to impersonate services or decrypt traffic.

Technologies: Red Hat Hawtio-Operator. Vendors: Red Hat.

Quick answers

Is CVE-2026-81320 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-81320 being exploited in the wild.
How severe is CVE-2026-81320?
Medium severity, with a CVSS score of 5.5, published 15 September 2026.
Which products and versions are affected?
Red Hat Hawtio-Operator <UNKNOWN>.
Is there a fix for CVE-2026-81320?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-81320 attacked?
It is attacked with local access.
Am I affected by CVE-2026-81320?
Check whether you run Red Hat Hawtio-Operator at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The hawtio-operator improperly serializes the entire Route object—including TLS private keys in PEM format—to JSON and writes it to stdout when log verbosity is set to debug level 1 or higher. This is a sensitive information logging vulnerability (CWE-532) where credential material is exposed in operator logs. The attack vector is local, requiring low privileges and access to pod logs or centralized log aggregation systems. An attacker with such access can extract the TLS private key and use it to impersonate the service or decrypt intercepted traffic. Mitigation includes setting log verbosity to 0 (default), rotating any exposed TLS secrets, and purging affected log entries.

Affected products

  • Red Hat hawtio-operator <UNKNOWN>

Timeline

  • 2026-09-15: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.