Insertion of sensitive information into log file vulnerability in Johnson Controls C-CURE 9000, Victor allows Use of Known Operating…
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected product is C-CURE 9000 / victor.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 19/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Johnson Controls C-CURE 9000 and Victor security software writes sensitive information into a log file, which lets an attacker use known operating system credentials. An attacker on the same network segment with low-privilege access can exploit this without any user interaction.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Insertion of sensitive information into log file vulnerability in Johnson Controls C-CURE 9000, Victor allows Use of Known Operating System Credentials.
This issue affects C-CURE 9000, Victor: 3.20.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 8.8
- No patch5/5No patch listed yet
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 29 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected product is C-CURE 9000 / victor.Workaround: The facts do not describe a workaround. Limit access to the product's log files until a fix or official guidance is available from Johnson Controls.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Johnson Controls C-CURE 9000, Victor
3.20
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-106019
Is CVE-2026-106019 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The product writes sensitive information into a log file, where it can be read by people who should not see it. The description also refers to use of a known operating system account or password, but the facts do not give further detail on that path.Source: johnsoncontrols.com
Which versions are affected by CVE-2026-106019?
C-CURE 9000, Victor: version 3.20.Source: cve.now feed data
Am I affected, and how do I check?
The facts name Johnson Controls C-CURE 9000 and victor as the affected products, but they give no version ranges. Check the installed product name and version in the product's about or version information to see whether your installation matches the listed products.Source: johnsoncontrols.com
How do I fix CVE-2026-106019?
The facts do not name a fixed version or an upgrade target. Check the Johnson Controls advisory for the product for the fixed release.Source: johnsoncontrols.com
What if there's no patch?
The facts do not describe a workaround. Limit access to the product's log files until a fix or official guidance is available from Johnson Controls.Source: johnsoncontrols.com