# CVE-2026-22306: Critical flaw impacting OZOLS ERP's automatic update channel

> Attackers can execute arbitrary code and steal data via the ERP's unsecured auto-update channel due to an abandoned domain and lack of integrity checks.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-xhj7-3r6j-f89h

## What is CVE-2026-22306?

CVE-2026-22306 is a critical vulnerability in OZOLS, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Download of code without integrity check, inclusion of functionality from untrusted control sphere, and cleartext 
transmission of sensitive information vulnerability in Ozols Grupa OZOLS
 on Windows caused by an abandoned auto-update domain. Affected
component: the automatic update channel - OzolsSQL client update path, the <db>_update SQL Server Agent job (@subsystem = N'ActiveScripting') and serv_update.vbs.

This issue affects OZOLS: before 1.1.1233.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere), CWE-494 (Download of Code Without Integrity Check), CWE-319 (Cleartext Transmission of Sensitive Information)

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


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

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

## Is CVE-2026-22306 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22306 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22306 is a critical vulnerability in OZOLS, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22306 exists.

Affected product: OZOLS. 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-22306/ (Markdown: https://insights.sbomify.com/CVE-2026-22306/index.md)
```

## Sources

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

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