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.
CVE-2026-81320
Score 5.5 from GitHub Security Advisory published 2026-09-15. a secondary CVSS source baseline 5.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.5
- EG Score
- 5.5(high)
- EG Risk
- 25(Track)EG Risk 25/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity55% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 3%
- KEV
- Not listed
Published
September 15, 2026
Last Modified
September 17, 2026
Advisory Details (2)
Auto-updated Sep 15, 20262524898 – (CVE-2026-81320) CVE-2026-81320 hawtio-operator: hawtio-operator: TLS private key written to operator log at debug level
https://bugzilla.redhat.com/show_bug.cgi?id=2524898CVE-2026-81320 - Red Hat Customer Portal
Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a
https://access.redhat.com/security/cve/CVE-2026-81320Vendor Advisories for CVE-2026-81320(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 19× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-20 12:29 UTCEG score recompute
- 2026-09-20 12:29 UTCGHSA enrichment
- 2026-09-19 14:49 UTCEG score recompute
- 2026-09-19 14:48 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 17:08 UTCGHSA enrichment
- 2026-09-17 19:27 UTCEG score recompute
- 2026-09-17 19:27 UTCGHSA enrichment
- 2026-09-17 18:48 UTCEG score recompute
- 2026-09-17 18:47 UTCGHSA enrichment
- 2026-09-16 19:58 UTCEG score recompute
- 2026-09-16 19:58 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-16 04:23 UTCEG score recompute
- 2026-09-16 04:23 UTCGHSA enrichment
- 2026-09-15 06:28 UTCEG score recompute
- 2026-09-15 05:43 UTCEG score recompute
- 2026-09-15 05:43 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-81320?
When was CVE-2026-81320 disclosed?
Is CVE-2026-81320 actively exploited?
What is the CVSS score of CVE-2026-81320?
How do I remediate CVE-2026-81320?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-81320
Is Your Infrastructure Affected by CVE-2026-81320?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.