# CVE-2026-22537: INFORMATION DISCLOSURE WITHIN THE OPERATING SYSTEM

> An attacker with maintenance access can read clear-text credentials and sensitive data from system files due to insufficient hardening.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jan 2026
- **Updated:** 7 Jan 2026
- **Also known as:** GHSA-hrg8-5gxf-r4xq

## What is CVE-2026-22537?

CVE-2026-22537 is a medium-severity vulnerability in EFACEC QC 60/90/120, published on 7 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The lack of hardening of the system allows the user used to manage and maintain the charger to consult different files containing clear-text credentials or valuable information for an attacker.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

## Which versions are affected by CVE-2026-22537?


## How do I fix CVE-2026-22537?

No fix has been published for CVE-2026-22537 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-22537 being exploited?

There is no known exploitation of CVE-2026-22537 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-22537 and fix it if it is affected.

What it is: CVE-2026-22537 is a medium-severity vulnerability in EFACEC QC 60/90/120, published on 7 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22537 in the wild and no public exploit code.

Affected product: EFACEC QC 60/90/120. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-22537/ (Markdown: https://insights.sbomify.com/CVE-2026-22537/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-22537
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22537
- OSV: https://osv.dev/vulnerability/CVE-2026-22537

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-22537/
Summaries are generated and may contain mistakes; the official description above is the record.