{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-81320 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-81320 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-81320 is a medium-severity vulnerability in Red Hat build of Apache Camel - HawtIO 4, published on 15 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-81320 and fix it if it is affected.\n\nWhat it is: CVE-2026-81320 is a medium-severity vulnerability in Red Hat build of Apache Camel - HawtIO 4, published on 15 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-81320 in the wild and no public exploit code.\n\nAffected product: Red Hat build of Apache Camel - HawtIO 4. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-81320/ (Markdown: https://insights.sbomify.com/CVE-2026-81320/index.md)","id":"CVE-2026-81320","markdown":"https://insights.sbomify.com/CVE-2026-81320/index.md","name":"CVE-2026-81320","record":{"aliases":["GHSA-75j7-xvw4-g5cm"],"analysis":{"component_type":"cloud_service","fix_type":"configuration_change","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Red Hat Hawtio Operator","requires_auth":"low_privilege","summary":"Attackers with log access can read TLS private keys if the operator runs at debug level, exposing sensitive cryptographic material.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Hawtio-operator: hawtio-operator: tls private key written to operator log at debug level","id":"CVE-2026-81320","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"CareCam CM2507 Cleartext Storage of Sensitive Information","id":"CVE-2026-81321"},"packages":[],"prev":{"headline":"Unsafe deserialization of decrypted terms enables node DoS in AshCloak","id":"CVE-2026-81319"},"products":["Red Hat build of Apache Camel - HawtIO 4"],"published":"2026-09-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-17","vendors":["Red Hat"]},"summary":"Attackers with log access can read TLS private keys if the operator runs at debug level, exposing sensitive cryptographic material.","url":"https://insights.sbomify.com/CVE-2026-81320/"}