# CVE-2026-22536: PRIVILEGE ESCALATION VIA SUDO COMMAND

> Attackers can escalate privileges via sudo due to missing permission controls in the EFACEC QC series configuration.

- **Severity:** High 8.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **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-44qw-vppw-hwhc

## What is CVE-2026-22536?

CVE-2026-22536 is a high-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 absence of permissions control for the user XXX allows the current configuration in the sudoers file to escalate privileges without any restrictions

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-22536 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22536 is a high-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-22536 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-22536/ (Markdown: https://insights.sbomify.com/CVE-2026-22536/index.md)
```

## Sources

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

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