LiveActive security incident?Get immediate response
CVE Record

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

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.

CriticalCVSS 10Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

OZOLS versions before 1.1.1233 on Windows may retrieve update code without verifying its integrity through infrastructure no longer controlled by the vendor. The update process may therefore accept untrusted code and transmit sensitive information in cleartext, threatening ERP availability, confidentiality, and connected systems.

Executive priority

Treat this as an immediate ERP security priority. Locate affected installations, confirm vendor remediation, and upgrade promptly. Because the update path crosses a lost trust boundary and permits high-impact outcomes without authentication or user action, investigate historical update activity rather than assuming upgrading alone resolves possible prior compromise.

Technical view

CVE-2026-22306 affects the OzolsSQL client update path, the <db>_update SQL Server Agent job using ActiveScripting, and serv_update.vbs. The chain combines unverified code retrieval, an abandoned update domain, and cleartext transmission. Its CVSS 4.0 score is 10.0: network-reachable, low-complexity, unauthenticated, and requiring no user interaction, with high direct and downstream impacts.

Likely exposure

Organizations running OZOLS before 1.1.1233 on Windows are within the stated affected range. Practical exposure depends on whether the specified update components are present and can contact the abandoned infrastructure. The bundle provides no deployment prevalence or exact affected-domain details. Versions 1.1.1233 and later are outside the stated range.

Exploitation context

KEV is false, and the bundle does not document observed exploitation. One OffSeq reference is tagged as an exploit reference, but the supplied evidence does not establish public weaponization or active attacks. Treat compromise status as unknown until relevant telemetry is reviewed.

Researcher notes

The trust failure combines CWE-494, CWE-829, and CWE-319: unverified code retrieval, reliance on an untrusted control sphere, and cleartext sensitive data. The exact abandoned domain, polling behavior, execution privileges, indicators, and remediation details are absent from the bundle. Validate these with Ozols Grupa and the cited advisory; component presence alone does not prove compromise.

Mitigation direction

  • Identify Windows systems running OZOLS versions earlier than 1.1.1233.
  • Confirm with Ozols Grupa that 1.1.1233 or later is the supported remediation, then upgrade promptly.
  • Ask Ozols Grupa whether the automatic update channel should be disabled pending remediation.
  • Preserve relevant DNS, proxy, endpoint, and SQL Server Agent logs for investigation.

Validation and detection

  • Verify installed OZOLS versions and confirm no systems remain below 1.1.1233.
  • Inventory the <db>_update SQL Server Agent job and serv_update.vbs across affected environments.
  • Review historical DNS and proxy telemetry for unusual OZOLS update-path communications.
  • Review endpoint and database-host telemetry for unexpected code or script execution associated with updates.
  • Confirm post-remediation update behavior against current Ozols Grupa guidance.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-319: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-494: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-829: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22306 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
10 (4.0)
Known Exploited
No
Published

Vector: 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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
10CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——ENISA
10CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96ENISA

Vulnerability scoring details

Base CVSS 4.0 score

10Critical
CVSS 4.0 vector shape for CVE-2026-22306Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Ozols GrupaOZOLS0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-319 · source CWE mapping

Cleartext Transmission of Sensitive Information

Cleartext Transmission of Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-494 · source CWE mapping

Download of Code Without Integrity Check

Download of Code Without Integrity Check represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-829 · source CWE mapping

Inclusion of Functionality from Untrusted Control Sphere

Inclusion of Functionality from Untrusted Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.