Skip to content
Applications

CVE-2026-22306

10.0
Critical
EPSS 0.16%Patch availableAug 21, 2026

Abandoned auto-update domain allows malicious updates and RCE in OZOLS (pre-1.1.1233).

common questions

Is CVE-2026-22306 being exploited?

Not confirmed. CVE-2026-22306 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.16% probability of exploitation in the next 30 days.

How severe is CVE-2026-22306?

CVE-2026-22306 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-22306?

Yes. A fix has been recorded for CVE-2026-22306. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-22306 affect?

CVE-2026-22306 affects OZOLS (versions before 1.1.1233), OzolsSQL client, SQL Server Agent job <db>_update (serv_update.vbs). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-22306?

Upgrade to OZOLS 1.1.1233+ immediately; disable auto-update and block legacy update domain

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
OZOLS (versions before 1.1.1233)OzolsSQL clientSQL Server Agent job <db>_update (serv_update.vbs)
impact

Remote code execution via malicious auto-update (serv_update.vbs / SQL Agent ActiveScripting) and cleartext data exposure; attackers can run arbitrary code and exfiltrate data.

action required

Immediate action required

affected versions
Ozols Grupa OZOLS
  • affected< 1.1.1233

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free