Bug 2524898 (CVE-2026-81320)

Summary: CVE-2026-81320 hawtio-operator: hawtio-operator: TLS private key written to operator log at debug level
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: abrianik, ggrzybek, jraez, parichar, security-response-team, tasato
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in hawtio-operator. When a custom Route TLS secret is configured and the operator runs at debug log level 1 or higher, the entire Route object — including the TLS private key in PEM format — is serialized to JSON and written to the operator's standard output. Operator logs are typically forwarded to centralized logging systems and readable by anyone with pods/log access in the openshift-operators namespace. Debug level 1 is a low threshold commonly enabled during troubleshooting.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-08-27 09:53:51 UTC
H-3 from Project Glasswing security audit of hawtio-operator. When a custom Route TLS secret is configured and the operator runs at -v=1 or higher, the entire Route object including spec.tls.key (PEM private key) is JSON-serialised into stdout. Operator logs are typically forwarded to centralised logging and readable by anyone with pods/log in openshift-operators. Source: hawtio-operator-security-audit.json#H-3.